From: Cameron Kaiser <spectre@stockholm.ptloma.edu>
Message-Id: <200208070540.WAA30788@stockholm.ptloma.edu>
Subject: [gopher] Re: Process question
In-Reply-To: <20020806135709.A6583@pongonova.net> from Brian at "Aug 6,
 2 01:57:09 pm"
To: gopher@complete.org
Date: Tue, 6 Aug 2002 22:40:48 -0700 (PDT)
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


> I have a process question about gopher, and gophermap specifically.  I'm
> tempted to automagically generate a new gophermap whenever I add new
> files/dirs to my gopher root dir.  From what I can tell, gophermap is an
> all-or-nothing deal:  If you use it, then everything you want accessible
> has to be part of gophermap.  If you don't,
> then everything in the gopher root is accessible.

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.

-- 
----------------------------- personal page: http://www.armory.com/~spectre/ --
 Cameron Kaiser, Point Loma Nazarene University * ckaiser@stockholm.ptloma.edu
-- Emulate your heroes, but not if they're dead. ------------------------------