Date: Mon, 11 Sep 2006 09:59:54 -0500
From: John Goerzen <jgoerzen@complete.org>
To: gopher@complete.org
Subject: [gopher] Re: embedded gopher servers
Message-ID: <20060911145954.GA18576@excelhustler.com>
References: <2c02a9ac0609110659m14203736nabfd2166d2b0ef81@mail.gmail.com>
 <200609111440.k8BEegUe014284@floodgap.com>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200609111440.k8BEegUe014284@floodgap.com>
User-Agent: Mutt/1.5.12-2006-07-14
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

On Mon, Sep 11, 2006 at 07:40:42AM -0700, Cameron Kaiser wrote:
> > Possibly a glaring oversight on the part of the openwrt distribution
> > people- they include an http server to run on the router, yet there
> > seems to be no trace of a gopher server for said distro.
> > 
> > Does anybody have any idea if such a package might exist for it? If
> > not, I'm not beyond poking at source code, but I'd rather not
> > re-invent the wheel
> 
> UMN gopherd is pretty much dead, but depending on your proclivities,

Yes, it will probably have the smallest footprint of all of these.

But you could go even smaller.  The gopher protocol is simple enough
that you could write a micro gopherd in C, from scratch, and not deal
with all the UMN complexities.

> Python fiends like pyGopher: gopher://gopher.quux.org/
> Perl demons might like Bucktooth (shameless plug):
> 	gopher://gopher.floodgap.com/
> 
> Both of these are relatively small and should fit within the firmware confines
> of an embedded system like this (you may need to cross-configure Bucktooth
> on a bigger box and import the outputted object, though).

The same holds for PyGopherd for a systemwide install, though if there
is a Python environment with the Socket API, you can probably just run
it in-place from its untarred directory.

-- John