[gopher] Re: Gopher Markup

[Jeroen Schot <schot@xxxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wed, Aug 12, 2009 at 12:18:48PM +0200, Jeroen Schot wrote:
> Yes{1}. Gopher URI's can be confusing. Keep in mind that the 'paht' [sic] is
> not a path per se but just a selector string that identifies a resource. No
> hierarchy is implied. 
> 
> {1} Although you could leave it out in which case it defaults to type '1'
> (gopher menu).

Sorry, what I said is wrong. The single character 'type' is only optional when
asking for the top-level selector (like gopher://gopher.floodgap.com). In all
other cases it is mandatory.

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. But do these two point to the same resource? Both bucktooth
and pygopherd seem to think so, but I can't find a reference for this in the
RFC's.

Regards,
- -- 
Jeroen Schot <schot@xxxxxxxxxxxxxxx>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)

iIwEAREIADQFAkqCrCQtGGh0dHA6Ly9zY2hvdC5hLWVza3dhZHJhYXQubmwvb3Bl
bnBncC9rZXkuYXNjAAoJEJbU8MDXM4Lxp+wA/RL7GIoIRtcTRDLlwgJEe3T0oVl0
44PEVPYXvz+kE1CFAP9+CYdE3lrJG9jMfSIoV6nKe0RqSfhCojzcPGHu0/nQxA==
=85qe
-----END PGP SIGNATURE-----