Re: [gopher] Draft RFC
On 21 June 2012 15:42, Alistair <alistair@alistairsserver.no-ip.org> wrote:
> On 21/06/2012 20:22, Nick Matavka wrote:
>>
>> It should be mandatory for a Gopher client to support LINKING TO
>> things that aren't gopher. HTTP clients (aka web browsers) do the
>> same thing.
>>
>> For instance, if you see a link like <mailto:asdf@example.co.uk> you
>> can click it and it will launch your eMail client. If you see a link
>> like <gopher://gopher.example.co.uk> it will launch your Gopher
>> client.
>
>
> This is by no means a universal capability. This relies on having software
> on the system able to service those protocols for a start, and the client
> knowing how to invoke them (or having an operating system that automagically
> launches the correct client).
>
> On a system with no multi-tasking capabilities launching an appropriate
> client could well mean terminating the current program and losing any
> current state too. I suppose one could handle it like following a link to a
> file - that is ask the user whether they want to launch a program to handle
> it or to go back (or in the case of a file save to local storage).
>
>
> _______________________________________________
> Gopher-Project mailing list
> Gopher-Project@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
Well, then, those clients are non-compliant with the Gopher2.0
standard; they are, however, Gopher1.0 compliant.
--
/^\/^\
\----|
_---'---~~~~-_
~~~|~~L~|~~~~
(/_ /~~--
\~ \ / /~
__~\ ~ / ~~----,
\ | | / \
/| |/ | |
| | | o o /~ |
_-~_ | || \ /
(// )) | o o \\---'
//_- | | \
// |____|\______\__\
~ | / | |
|_ / \ _|
/~___| /____\
_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
Reply to: