[gopher] Updated Gopher RFC

[Kim Holviala]

On May 9, 2012, at 9:11 , Driedfruit wrote:

>>>> You're forgetting something: gopher is nothing but a straight
>>>> through unrestricted two-way TCP connection between a gopher CGI
>>>> app and the client. Why would you complicate things by encoding
>>>> stuff and resubmitting when you can just keep the connection open?
>>>> 
>>> 
>>> Please forgive my ignorance, that makes a lot of sense! But I'm
>>> still a bit confused, how would one implement such workflow? I
>>> understand the CGI keeping connection open and reading from stdin
>>> part, but not the client sending raw data part. Could you elaborate?
>> 
>> To my understanding (I stopped coding for living years ago)
>> JavaScript these days has TCP sockets.
> 
> I might be completely off my mark here, but no, I don't think it does.
> If it did, Overbite extensions would've implemented gopher directly in
> JavaScript instead of redirecting to web gateways.

Uh-oh, you're right. And people still think Javascript is a good idea? Damn...

Well, both Flash and Java have real sockets, and you can offer both through gopher. I know my idea is a bit far-fetched, but in theory it should work.



Kim