Received: with ECARTIS (v1.0.0; list gopher); Mon, 24 Dec 2007 07:23:52 -0600 (CST) Received: from wsip-68-99-116-150.ks.ok.cox.net ([68.99.116.150] helo=heinrich.lan.complete.org) by glockenspiel.complete.org with esmtps (with TLS-1.0:RSA_AES_256_CBC_SHA1:32) (TLS peer CN christoph.complete.org, certificate verified) (Exim 4.63) id 1J6nHP-0000qk-IW; Mon, 24 Dec 2007 07:23:49 -0600 Received: from jgoerzen by heinrich.lan.complete.org with local (Exim 4.68) id 1J6nHI-00038i-Gk; Mon, 24 Dec 2007 07:23:32 -0600 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> X-Spam-Status: No (score -0.7): AWL=-0.720 X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Mon, 24 Dec 2007 07:23:49 -0600 X-archive-position: 1767 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: jgoerzen@complete.org Precedence: bulk Reply-to: gopher@complete.org List-help: <mailto:ecartis@complete.org?Subject=help> List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe> List-software: Ecartis version 1.0.0 List-Id: Gopher <gopher.complete.org> X-List-ID: Gopher <gopher.complete.org> List-subscribe: <mailto:gopher-request@complete.org?Subject=subscribe> List-owner: <mailto:jgoerzen@complete.org> List-post: <mailto:gopher@complete.org> List-archive: <http://www.complete.org/mailinglists/archives/> X-list: gopher

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