Received: with ECARTIS (v1.0.0; list gopher); Sun, 23 Dec 2007 17:56:14 -0600 (CST) Received: from static-71-170-11-156.dllstx.dsl-w.verizon.net ([71.170.11.156] helo=turquoise.pongonova.net) by glockenspiel.complete.org with esmtp (Exim 4.63) id 1J6ag0-0000F4-4i for gopher@complete.org; Sun, 23 Dec 2007 17:56:14 -0600 Received: by turquoise.pongonova.net (Postfix, from userid 1000) id 7C460726; Sun, 23 Dec 2007 17:56:58 -0600 (CST) 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 X-Spam-Status: No (score 0.6): AWL=0.000, NO_REAL_NAME=0.55 X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Sun, 23 Dec 2007 17:56:14 -0600 Content-Transfer-Encoding: 8bit X-archive-position: 1765 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: brian@pongonova.net 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 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