[gopher] Re: Gopher Markup

[Mateusz Viste <mateusz@xxxxxxxxxxxxxxxx>]

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

On Wednesday 12 August 2009 13:48 (CEST), Jeroen Schot wrote:
> There is one thing that still confuses me though. The gopher URI scheme says
> nothing about a '/' between the type character and selector string. So both
> gopher://gopher.quux.org/1/Archives and gopher://gopher.quux.org/1Archives are
> valid gopher URI's. 

Yes, they are.

> But do these two point to the same resource? 

No. One selector is "/Archives", while the other is "Archives". These are NOT 
the same selectors, although some (most?) server's implementations will be 
tolerant and threat them as the same.

> Both bucktooth  
> and pygopherd seem to think so, but I can't find a reference for this in the
> RFC's.

Because it's an implementation issue.
You don't even have to use path-like selectors, it's up to the server to decide 
what is his selector. A totally valid selector could also look like 
"blah/blah\sel*boom!.o&-:)".
Of course, most, if not all, servers are simply using paths as selectors, 
because it's the easy way to go, but it's not an obligation of any kind.

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

iQEcBAEBAgAGBQJKgrACAAoJEC30Ty9xnkvb29kH/ilEI6Ts2HeFOiKIBfcb8o5R
WA8E8Rs/H5ICfFYr8ks4vqxLVb6h309xPGUCVVxpyDwH3rKm1i4ryYc946IMgLvG
NKT7zK8q+HlAn4/emwitRw/bEQ0gaAr7TO2DSC2Ho7MZ4Rtfi4gmtra/eRGVJr6A
o1fYX+c1vjGQGeQS9Yk3cfVeQetn2PTeSx7hIrLYcvxvEb6NfKMdob4i20HDg52S
Lufk5+7Ez/UhMXysrSXEMMD1+HWxXa7wqb+TCbfGkE0jXPayCsrixZUztwaiqvGZ
/Pm0mAXO4EO8G0krDYfgRAztjEj/6zHIu8BwUT4M1FR+1qyjQI6J4m7UXqs0K30=
=fPMl
-----END PGP SIGNATURE-----