Message-ID: <43771901.4000903@versateladsl.be>
Date: Sun, 13 Nov 2005 11:44:17 +0100
From: Walter Vermeir <vt6115514@versateladsl.be>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013)
MIME-Version: 1.0
To: gopher@complete.org
Subject: [gopher] Re: Gopher for dummies
References: <43761C9A.2000909@versateladsl.be>
 <20051112181841.GA2411@freeshell.org>
In-Reply-To: <20051112181841.GA2411@freeshell.org>
Content-type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

R.A.Pavlov schreef:

>SDF runs Pygopherd now and that's very cool because this server supports
>both popular gopher link file formats - .links and .names files from
>original UMN gopherd and gophermap files from Bucktooth. To my mind,
>.links syntax is extremely cumbersome and irregular, it is described
>e.g. here
>
>gopher://gopher.quux.org/0/devel/gopher/pygopherd/SVN/doc/pygopherd.txt
>
>Gophermap file syntax is very simple and it's described here
>
>gopher://gopher.floodgap.com/0/buck/dbrowse%3ffaquse%201
>  
>
Thanks. This is useful information.

But the practical examples are very limited.  The best way to see how
thinks works it to look at the source.  It would be very interesting if
I could get the source files of a decent gopher site like

gopher://gopher.floodgap.com:70/1/

Greetings,
Walter Vermeir