From: Cameron Kaiser <spectre@stockholm.ptloma.edu>
Message-Id: <200101151723.JAA08238@stockholm.ptloma.edu>
Subject: [gopher] Re: Gopher "robots.txt"
In-Reply-To: <20010114220929.B885@success-info.com> from emanuel at heatdeath
 organisation at "Jan 14, 1 10:09:29 pm"
To: gopher@complete.org
Date: Mon, 15 Jan 2001 09:23:35 -0800 (PST)
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


> AFAIK there is only active gopher robot out there, which is floodgap's
> V2.  This is quite a nice situation to be in for doing things right.  If
> we want to keep this good situation, a gopher robot library should be
> created that any other robots would make use of, which encapsulates the
> complexity of this stuff.
> 
> Also, I don't think it would be that difficult to add minimal Gopher+
> support to a server, just enough to deliver basic attribute information
> needed to support the robot.

Well, for the sake of argument, say we accept the Gopher+ attributes approach.
That would work on a per-menu basis, which means V2 doesn't have to cache
and I can live with that. Will that satisfy John's concerns about setting
up robot access restrictions to mirrors?

-- 
----------------------------- personal page: http://www.armory.com/~spectre/ --
 Cameron Kaiser, Point Loma Nazarene University * ckaiser@stockholm.ptloma.edu
-- Injustice anywhere is a threat to justice everywhere. -- M. L. King, Jr. ---