[gopher] Updated Gopher RFC

[Nuno J. Silva]

On 2012-05-08, Alistair wrote:

> On 08/05/2012 17:01, zack mayson wrote:
>> Gopher is generally designed to be a low overhead protocol; plus, it
>> would introduce incompatibilities in clients running on old computers
>> (i.e. Zilogs, Sinclairs) and specifying what kind of data/files/content
>> X is neans a lot less work for client Y.
>>
>
> Trouble is there's a gazillion kinds of file and soon you end up with
> a huge mess like mimetypes.

The good thing about mimetypes is that they're easier to expand without
breaking compatibility (although, given enough time, one can always
break anything).

> As ling as a client or whatever knows what it /can/ handle it can just
> ignore anything it doesn't recognise.

The key is to grow a set of itemtypes such that clients can readily
ignore everything else and just focus on what they can handle.


-- 
Nuno J. Silva (aka njsg)
gopher://sdf-eu.org/1/users/njsg
http://njsg.sdf-eu.org/