From: Cameron Kaiser <spectre@floodgap.com>
Message-Id: <200712232350.lBNNouSL012062@floodgap.com>
Subject: [gopher] Re: Final dot required on server request?
In-Reply-To: <20071223234049.GA10710@pongonova.net> from "brian@pongonova.net"
 at "Dec 23, 7 05:40:49 pm"
To: gopher@complete.org
Date: Sun, 23 Dec 2007 15:50:56 -0800 (PST)
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

> 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.

My interpretation of the standard is that it is recommended, but that
clients should still handle an end-of-data condition gracefully.

To this end, I've deliberately taken a compromise view in Bucktooth where
"text" data has the final "." but binary data (or what Bucktooth perceives
is binary) does not, for those clients that simply suck all data and
assume that's the file.

However, PyGopherd would also be spec-compliant insofar as the clients
should handle the condition.

-- 
------------------------------------ personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser@floodgap.com
-- This signature is free of dihydrogen monoxide! Ban it now! www.dhmo.org ----