Message-ID: <02a701c845c5$58f73910$6901a8c0@YTHERIX>
From: "Trevor" <greendragon@stny.rr.com>
To: <gopher@complete.org>
References: <20071223234049.GA10710@pongonova.net>
Subject: [gopher] Re: Final dot required on server request?
Date: Sun, 23 Dec 2007 19:20:37 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

that's really odd. nearly every gopher server i've connected to stays with 
the RFC, which indicates the terminating dot is required.

however, gopher is a connectionless protocol. you connect, the server sends 
and disconnects. so i suppose technically, you don't need the ending period, 
you just need to read the socket until the connection closes.

trevor

----- Original Message ----- 
From: <brian@pongonova.net>
To: <gopher@complete.org>
Sent: Sunday, December 23, 2007 6:40 PM
Subject: [gopher] Final dot required on server request?


>I noticed that PyGopherd does not appear to send a final "." character
> prior to terminating the connection, but Bucktooth does.  A quick read
> of the RFC leads me to believe the "." is to be expected.  Has this
> been deprecated?  It's not a big deal, just need to know how to write
> a bit of code to either expect or not expect the dot.
>
>  --Brian
>