Re: [gopher] Updated Gopher RFC
I am not really a fan of such brutal connexion closing...
It's what HTTP/1.0 do (or HTTP/1.1 with connection: close header).
The nice thing about the dot is that it provides a very easy information to the client - whether or not the menu has been completely transferred. And this requires very minimal logic into the client.
Then, the problem is that clients are now discarding such dot, because there are servers out there that don't apply to the RFC, and just close the connection without any warning...
Mateusz
On Tuesday 08 May 2012 19:51:46 Kim Holviala wrote:
> On May 8, 2012, at 20:16 , Wolfgang Faust wrote:
>
> > Gaack! This discussion is precisely why we need an updated standard. The mess of itemtypes, in particular, is rather awful. I'll take a look at the docs on Kim's server at some point. In the meantime, is there a definitive standard for the period that terminates some connections?
>
> In short, I don't, I just close the connection. The client has no other choise but to consider the transfer done.
>
> Or, not me, I don't whistle to to the modem. Anymore. Nor clap my hands to scare teh butterflies.
>
> Uh..
>
> My server, Gophernicus, just closes the connection. Less extra dots to worry about. If you really think about it, what would the server or the client do after the dot? Nothing, so why not just forgetaboutit and close the session.
>
>
>
> - Kim
>
>
>
> _______________________________________________
> Gopher-Project mailing list
> Gopher-Project@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
>
>
_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
Reply to: