Received: with LISTAR (v1.0.0; list gopher); Mon, 21 May 2001 10:46:24 -0500 (EST) Return-Path: <emanuel@siva.heatdeath.org> Delivered-To: gopher@complete.org Received: from siva.heatdeath.org (ajhn27jly44ne.bc.hsia.telus.net [64.180.116.11]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id F2F763B80B for <gopher@complete.org>; Mon, 21 May 2001 10:46:23 -0500 (EST) Received: from emanuel by siva.heatdeath.org with local (Exim 3.22 #1) id 151rt1-0004eN-00 for gopher@complete.org; Mon, 21 May 2001 08:46:23 -0700 Date: Mon, 21 May 2001 08:46:23 -0700 From: "em@nuel" <em@nuel.ca> To: gopher@complete.org Subject: [gopher] Re: web->gopher Message-ID: <20010521084623.B15451@siva.heatdeath.org> Mail-Followup-To: "em@nuel" <em@nuel.ca>, gopher@complete.org References: <20010520231206.B10530@siva.heatdeath.org> <87itiud876.fsf@complete.org> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <87itiud876.fsf@complete.org>; from jgoerzen@complete.org on Mon, May 21, 2001 at 10:37:33AM -0500 Content-Transfer-Encoding: 8bit X-archive-position: 162 X-listar-version: Listar v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: em@nuel.ca Precedence: bulk Reply-to: gopher@complete.org List-help: <mailto:listar@complete.org?Subject=help> List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe> List-software: Listar version 1.0.0 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 Mon, May 21, 2001 at 10:37:33AM -0500, John Goerzen wrote: > Your Gopher+ question about the bug in gopherd is a sticky one. I may > have to look into it, but the question as to how to handle that in the > client is a tricky one because many gophers out there are not actively > maintained and won't see the update even if gopherd is fixed. I'm not > sure what to suggest just yet.

Yeah... it looks like I'll have to put in a workaround. Something like download the whole thing and lop off the period at the end if there is one and it's a text file (basically treat it just like a plain Gopher response). Too bad, it's a nice feature of Gopher+ that would work well if we ever need to implement keep-alive connections (not that I can see any reason for that with Gopher.).