Date: Sun, 23 Dec 2007 17:56:58 -0600
From: brian@pongonova.net
To: gopher@complete.org
Subject: [gopher] Re: pygopherd & ASK
Message-ID: <20071223235658.GA10815@pongonova.net>
References: <20030828184443.GA17767@pippuri.mawhrin.net>
 <20030828192103.GD13821@wile.excelhustler.com>
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030828192103.GD13821@wile.excelhustler.com>
User-Agent: Mutt/1.5.5.1i
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

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