Received: with ECARTIS (v1.0.0; list gopher); Thu, 06 Mar 2003 13:06:41 -0600 (CST) Return-Path: <jgoerzen@excelhustler.com> X-Original-To: gopher@complete.org Delivered-To: gopher@complete.org Received: from wile.excelhustler.com (unknown [68.99.114.105]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by gesundheit.complete.org (Postfix) with ESMTP id 0265C18320DA; Thu, 6 Mar 2003 13:06:41 -0600 (CST) Received: by wile.excelhustler.com (Postfix, from userid 1000) id 8AAE47790; Thu, 6 Mar 2003 13:06:28 -0600 (CST) Date: Thu, 6 Mar 2003 13:06:28 -0600 From: John Goerzen <jgoerzen@complete.org> To: gopher@complete.org Subject: [gopher] Re: PyGopherd 2.0 roadmap Message-ID: <20030306190628.GB6802@wile.excelhustler.com> References: <E18r08x-0002bW-00@odie.runbox.com> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <E18r08x-0002bW-00@odie.runbox.com> User-Agent: Mutt/1.4i Content-Transfer-Encoding: 8bit X-archive-position: 734 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: jgoerzen@complete.org 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 06:30:59PM +0000, Timm Murray wrote: > > 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.

I mean literally CGI. The idea is to pass CGI-standard environment variables to programs, and let them output Gopher code -- a gopher directory or file, handling the typing themselves.

This would mean people to use, to a certain extent, existing CGI libraries for coding.

Maybe it's not necessary. I'm curious how PHP was coerced to run under Bucktooth, really :-)

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

We've already got three: * UMN style * Bucktooth style * PYG (PyGopherd python style)