From: John Goerzen <jgoerzen@complete.org>
To: gopher@complete.org
Subject: [gopher] Re: Final dot required on server request?
Date: Mon, 24 Dec 2007 07:23:32 -0600
User-Agent: KMail/1.9.7
Cc: Cameron Kaiser <spectre@floodgap.com>
References: <200712232350.lBNNouSL012062@floodgap.com>
In-Reply-To: <200712232350.lBNNouSL012062@floodgap.com>
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Message-Id: <200712240723.32496.jgoerzen@complete.org>
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

On Sunday 23 December 2007 05:50:56 pm Cameron Kaiser wrote:
>
> 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.

I believe that PyGopherd does the same thing, and in fact that it does so 
because a reading of the source code of UMN gopherd indicated that's how 
*it* behaves.

Note too that gopher+, which PyGopherd supports at least part of, alters this 
because it is possible to send file size information with it.

-- John