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
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


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