[gopher] Re: pygopherd 0.3.1

[Ralph Furmaniak <sugaku@xxxxxxxxxxxx>]

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.