Complete.Org: Mailing Lists: Archives: gopher: August 2002:
[gopher] Re: Process question

[gopher] Re: Process question

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: Process question
From: "Aaron J. Angel" <aangel@xxxxxxxxxxxxx>
Date: Wed, 07 Aug 2002 01:23:25 -0500
Reply-to: gopher@xxxxxxxxxxxx

> Since bucktooth is the originator of the gophermap 'standard' and since I'm
> the originator of bucktooth :-), I feel authoritative enough to say that
> your understanding squares with the present implementation.
> Now, to be sure, the UMN-style gopher menus should work in the same fashion,
> however, if memory serves.

As far as the UMN handler goes, that's not quite accurate.  UMN-style 
gopher menus are contained in multiple files, and are merged with the 
dynamically generated menus, as opposed to bucktooth's all-or-nothing 
model, which is really why PyGopherd's inclusion of both methods is 
quite nifty.

[Prev in Thread] Current Thread [Next in Thread]