[gopher] Re: pygopherd & ASK (fwd)

[Cameron Kaiser <spectre@xxxxxxxxxxxx>]

An old message I found while cleaning out my inbox that might be worth
resurrecting. We're still trying to find the next step, and Gopher+ is
still something somewhat controversial. I forgot that John had proposed
this idea once upon a time.

----- Forwarded message from brian@xxxxxxxxxxxxx -----

Date: Sun, 23 Dec 2007 17:56:58 -0600
From: brian@xxxxxxxxxxxxx
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: pygopherd & ASK
Message-ID: <20071223235658.GA10815@xxxxxxxxxxxxx>

On Thu, Aug 28, 2003 at 02:21:03PM -0500, John Goerzen wrote:
> That is, you take the RFC1436 standard gopher and tack on new fields at the
> end for the file size, its MIME type, encoding, and language.  Should be
> easy enough to parse and ignore as the case may be.

Has there been any more discussion about this?  These basic fields
would make gopher much more efficient and easier to work with...as it
is, clients that communicate with web browsers must determine these
fields prior to sending binary data to the browser, a most inefficient
use of processing time (since the file has to be read into a buffer
first to determine file size).

Or at least that's the only way I've been able to do it...if someone
knows how to send binary data via a proxy to a browser without
determining these fields first, I'd love to hear how it's done.

  --Brian


----- End of forwarded message from brian@xxxxxxxxxxxxx -----

-- 
------------------------------------ personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser@xxxxxxxxxxxx
-- Drive defensively ... buy a tank. ------------------------------------------