[gopher] Re: How to handle lines beginning by a dot?

[Mateusz Viste <mateusz@xxxxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 29 January 2009 02:23, Cameron Kaiser wrote:
> That is a fascinating question. There is no <crlf> after it, so I would say
> print it as is, a one-byte binary file if you like.

Well, the idea of the question was rather "how to handle a dot-cr-lf line in a 
document which has to be served by Gopher?" :-)
Say, we have a file like that:
- ----
Blah blah<CR/LF>
blah<CR/LF>
.<CR/LF>
blah<CR/LF>
- ----

There's a line which contains a single dot, followed by CR/LF chars... If I 
would be a Gopher server, how would I handle that? If I send that as-is, then 
there is a pretty big risk that the client will cut the file after that 
"dot-CR/LF" line, thinking that it is the end of transmition...

Matjaž proposed to turn such line into "dot-space-CR/LF". Indeed, that's an 
interesting solution, as it doesn't change anything visually for the end user, 
and make sure that the gopher client won't be fooled...

Best regards,
Mateusz Viste
- -- 
You'll find my public OpenPGP key at gopher://gopher.viste-family.net/PGP
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iQEcBAEBAgAGBQJJhInvAAoJEC30Ty9xnkvb/W4H/2NHXCFX2+pLTKKcIjpDTnYe
Cl+XQAghyHthWbczfdTRVPK4WYvdEfl76aj2p+ah8H6v7meulebrWfE46CMjbTsK
Nr4L40/ptlP6Q0C0JDgLuYjN/QlJKD3WiMieSdT1o0cCbYbFWm+NvzYbpFFytYct
o4580LKMAMSor0YpivAsedM2dEY4wp34HsT7ebVhjg7EyWW7Up1LL121d9BWj3a8
YwmfHUZRNXEqwloAbxZgiHO7zoDGlH3MAuU5NAj1w3RIqnBM31QKxfMR4s6XET3I
p7Wj+oXZjdBZvQxtcyBPNAAeS6vD+CQM7lIgBMx9P5al9FLKTvy3J5i+zb9FHSM=
=YVdH
-----END PGP SIGNATURE-----