Received: with ECARTIS (v1.0.0; list gopher); Thu, 06 Mar 2003 12:31:31 -0600 (CST) Return-Path: <hardburn@runbox.com> X-Original-To: gopher@complete.org Delivered-To: gopher@complete.org Received: from aibo.runbox.com (snoopy.runbox.com [193.71.199.138]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client did not present a certificate) by gesundheit.complete.org (Postfix) with ESMTP id C039918320DA for <gopher@complete.org>; Thu, 6 Mar 2003 12:31:30 -0600 (CST) Received: from [10.9.9.15] (helo=odie.runbox.com) by lufsen.runbox.com with esmtp (Exim 4.12) id 18r09E-0002oQ-00 for gopher@complete.org; Thu, 06 Mar 2003 19:31:16 +0100 Received: from mail by odie.runbox.com with local (Exim 4.12) id 18r08x-0002bW-00 for gopher@complete.org; Thu, 06 Mar 2003 19:30:59 +0100 Content-type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: "Timm Murray" <hardburn@runbox.com> To: gopher@complete.org Subject: [gopher] Re: PyGopherd 2.0 roadmap Date: Thu, 06 Mar 2003 18:30:59 GMT X-Sender: 79977 X-Mailer: RMM Message-Id: <E18r08x-0002bW-00@odie.runbox.com> X-Sender: unknown X-archive-position: 733 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: hardburn@runbox.com 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, Mar 06, 2003 at 07:03:03PM +0100, smoerk wrote: > > and in the end it is more a http server than a gopher server? >=20 > Well, it's been both all along. The HTTP mode is there just for people t= hat > don't have Gopher capabilities, but you can (and have been able to) publi= sh > Web documents on it. >=20 > I hope that you'll be able to, for instance, take a CGI that outputs > gopher directories and view ir properly via HTTP.

I think "CGI" is the wrong term to use here. CGI is a standard that is tie= d=20 closely to HTTP. While some ideas of CGI can be used (like writing to STDOU= T), we=20 need a way to execute arbitrary code that better supports the peculiarities= of Gopher.

For instance, how will a "Gopher CGI" give it's data type. HTTP handles th= is by=20 having the script output a "Content-type" header. Outputting a similar hea= der=20 in Gopher would mean the program would have to be excuted every time just t= o=20 get a directory listing.

So I think we need to come up with a new standard for excuting programs and= call it=20 something other than "CGI". It should be easy enough to explain to people = that=20 "foo" standard is just Gopher's version of CGI.