[gopher] Draft RFC

[Nick Matavka]

On 21 June 2012 16:51, Nuno J. Silva <nunojsilva at ist.utl.pt> wrote:
>
> On 2012-06-21, Nick Matavka wrote:
>
>> On 21 June 2012 14:06, Alistair <alistair at alistairsserver.no-ip.org> wrote:
> [...]
>> In the WORST-CASE scenario ("non-compliant"):
>> Gopher1.0 client does not understand URL:, nor does it understand what
>> to do with HTML or how to launch a Web browser.  In that case, as you
>> said, Alistair, the gopher client will ignore it.  HOWEVER, the
>> Gopher1.0 client is non-compliant with the standard.
>>
>> Gopher1.5 server does not know the HTML workaround.  Gopher1.0 client
>> happens upon the URL: and doesn't know what to do with it.  HTML
>> workaround is not sent, and Gopher1.0 client can't follow the link.
>
> If it supports h but does not know about URL:, won't it just request the
> URL:... selector as a regular selector and be served the workaround HTML
> document?
>
> --
> Nuno J. Silva (aka njsg)
> gopher://sdf-eu.org/1/users/njsg
> http://njsg.sdf-eu.org/
>
> _______________________________________________
> Gopher-Project mailing list
> Gopher-Project at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project

I was talking clients that didn't support h.  h-supporting clients are
"semi-compliant"--they support h, but not url:.

-- 
       /^\/^\
       \----|
   _---'---~~~~-_
    ~~~|~~L~|~~~~
       (/_  /~~--
     \~ \  /  /~
   __~\  ~ /   ~~----,
   \    | |       /  \
   /|   |/       |    |
   | | | o  o     /~   |
 _-~_  |        ||  \  /
(// )) | o  o    \\---'
//_- |  |          \
//   |____|\______\__\
~      |   / |    |
       |_ /   \ _|
     /~___|  /____\