Received: with ECARTIS (v1.0.0; list gopher);
 Wed, 03 Apr 2002 14:12:02 -0500 (EST)
Return-Path: <sugaku@sympatico.ca>
Delivered-To: gopher@complete.org
Received: from tomts15-srv.bellnexxia.net (tomts15.bellnexxia.net
 [209.226.175.3])
	by pi.glockenspiel.complete.org (Postfix) with ESMTP id 1BEFB3B80B
	for <gopher@complete.org>; Wed,  3 Apr 2002 14:12:02 -0500 (EST)
Received: from [209.226.175.18] by tomts15-srv.bellnexxia.net
          (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP
          id
 <20020403191201.KWMO24482.tomts15-srv.bellnexxia.net@[209.226.175.18]>
          for <gopher@complete.org>; Wed, 3 Apr 2002 14:12:01 -0500
From: Ralph Furmaniak <sugaku@sympatico.ca>
To: gopher@complete.org
Subject: [gopher] Re: pygopherd 0.3.1
Date: Wed, 3 Apr 2002 14:12:00 EST
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Message-Id: 
 <20020403191201.KWMO24482.tomts15-srv.bellnexxia.net@[209.226.175.18]>
X-archive-position: 550
X-ecartis-version: Ecartis v1.0.0
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
X-original-sender: sugaku@sympatico.ca
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


Nice, we need some new servers.  Unfortunately it does not run for me.

You will now be getting into some of the fun parts, especially setting it up for views.  I found that attaching the type to the selector (like umn gopherd) can be invaluable do determine whether or not to format it as a directory (during translation to gopher+ and HTTP).

It works well to have a single output function which automatically takes in text or gophermap type selectors and formats it appropriately (or just prints it for type != 1), this way you can simply serve everything up (CGI, files included).

Taking your example I reprogrammed bucktooth to make it less monolithic, more "modular", and much more stable and efficient.  It is in testing now, but I will not have much time to work on it for a while.  Almost the only original code left is Cameron's copyright notice <g>. It should be able to work with windows when ready.

It includes:
full support for umn .cap and .link files
simple installation
significant performance increase
ability to run through inetd or on it's own as a daemon
almost exactly the same command-line options as gopherd
themable HTTP output
something more interesting: themable VRML output (think gophervr but better)
displaying of searches, asks, and views for gopher0 and http clients
completely configurable messages.
HTTP headers for content-length, content-type, ...
follows CGI format for executables (environment variables set, reads in input, processes headers IF they exist).

It can also display menus on other servers, so can be used as a makeshift client by going through your http server.  Clients can make use of this.