James Milne | 12 May 08:08 2001

Trying to figure out setting up Gopher server


I'm interested in using Gopher for a few projects I have in mind, but
I'm having some trouble figuring out how to actually set things up.

First off, I'm currently trying to run gopherd 2.3.1 on Solaris
2.6. I managed to get it up and running from reading the man files,
and have a pretty basic setup for testing right now. I'm still
confused on a number of things though.

I started out by creating a few directories off /gopher-data and put
some smallish text files in them. Then I created a .link file in
/gopher-data. It looks like this:

Name=Net.txt
Type=0
Host=gopher2
Port=70
Path=0/Net.txt
Numb=1

Two boxes running, this .link file would be on gopher1, so I've got a
link pointing to a file on the second machine. (Likewise, gopher2 is
pointing to a file on gopher1.)

When I pull everything up in Lynx, I get this:

                                  Gopher Menu

(FILE) Net.txt (DIR) HTML-files
 (DIR) Text-files
(Continue reading)

John Goerzen | 14 May 17:07 2001

Re: Trying to figure out setting up Gopher server


Good morning James!

James Milne <jmilne@...> writes:

> I'm interested in using Gopher for a few projects I have in mind, but
> I'm having some trouble figuring out how to actually set things up.

Glad to hear it!

> When I pull everything up in Lynx, I get this:
> 
>                                   Gopher Menu
> 
> (FILE) Net.txt (DIR) HTML-files
>  (DIR) Text-files

I should mention here that it is a known bug in Lynx that the first
two items in a Gopher menu are displayed on a single line.  That
happens everywhere.

> sorta explain what everything is, etc. I haven't found the
> documentation on how to do that, or perhaps I haven't understood the
> documentation on how to do that.

It's probably not documented :-)

Gopher, the original gopher protocol, has various document types -- 0
for text, 1 for directory, etc.  There is a type 'i' that is used for
information.  With UMN gopherd, you can create a file that looks like
(Continue reading)

em@nuel | 21 May 08:12 2001
Picon

web->gopher


Some of you may remember the web->gopher gateway I was working on some
months back.  Well, I just woke it up.  It had been dormant in the
middle of a bunch of work to improve the code and add proper Gopher+ for
some time now, and I just tied up a bunch of loose ends today.

So, except for Ask blocks, web->gopher now supports all of Gopher+, that
I know of.  You can view extended information such as attributes,
specify which view of a file you want to see, etc.  The interface isn't
as nice as I'd like, but it's there.  Gopher+ is soooo nice.

It's also useful for downloading large files and directories now.
Before web->gopher would read all the data from the gopher server into
the web server's memory, then dump the results to the browser.  Now it
streams nicely.  I'm presently streaming a 192kbps MP3 from my gopher
server through web->gopher to WinAmp, and it's all perfectly happy.  I
have yet to load test it, though.

Some stuff is gone, such as the tree interface.  It will probably make a
comeback in the future, though possibly in a different way.

I did a bunch of testing, and everything that broke I either fixed or
concluded was a bug in the server (or a bug in my understanding of the
Gopher+ protocol).  Yes, I need to make it a bit more forgiving with its
protocol handling, and it's not very friendly in parts (for example,
downloading an empty directory gives you... an empty screen!), but it
seems to work well.  Well enough that I'll soon disappear my web site
(which is mostly gone anyway) to be replaced with web->gopher.

Anyway, please give it a try:
(Continue reading)

Cameron Kaiser | 21 May 17:25 2001

Re: web->gopher


> Anyway, please give it a try:
> 
> http://heatdeath.org/

Cool, I'll drop by sometime today. Incidentally, I'm working on a gopher
client for the Commodore 64 (this is not a joke -- I finished a web
browser for it already, see

	http://www.armory.com/%7Espectre/cwi/hl/

). By comparison, gopher should be a piece of cake.

--

-- 
----------------------------- personal page: http://www.armory.com/~spectre/ --
 Cameron Kaiser, Point Loma Nazarene University * ckaiser@...
-- Too much of a good thing is wonderful. -- Mae West -------------------------

John Goerzen | 21 May 17:37 2001

Re: web->gopher


"em <at> nuel" <em@...> writes:

> Some of you may remember the web->gopher gateway I was working on some
> months back.  Well, I just woke it up.  It had been dormant in the
> middle of a bunch of work to improve the code and add proper Gopher+ for
> some time now, and I just tied up a bunch of loose ends today.

It looks way cool!  Glad to see it back alive!

Your Gopher+ question about the bug in gopherd is a sticky one.  I may
have to look into it, but the question as to how to handle that in the
client is a tricky one because many gophers out there are not actively
maintained and won't see the update even if gopherd is fixed.  I'm not
sure what to suggest just yet.

-- John

em@nuel | 21 May 17:46 2001
Picon

Re: web->gopher


On Mon, May 21, 2001 at 10:37:33AM -0500, John Goerzen wrote:
> Your Gopher+ question about the bug in gopherd is a sticky one.  I may
> have to look into it, but the question as to how to handle that in the
> client is a tricky one because many gophers out there are not actively
> maintained and won't see the update even if gopherd is fixed.  I'm not
> sure what to suggest just yet.

Yeah... it looks like I'll have to put in a workaround.  Something like
download the whole thing and lop off the period at the end if there is
one and it's a text file (basically treat it just like a plain Gopher
response).  Too bad, it's a nice feature of Gopher+ that would work well
if we ever need to implement keep-alive connections (not that I can see
any reason for that with Gopher.).

Cameron Kaiser | 21 May 17:55 2001

Re: web->gopher


By the way, I just discovered a mail in my spam-filter from you about some
problem with the World Gopher list. I fixed it and it seems to work now --
sorry about that. Typo :-)

--

-- 
----------------------------- personal page: http://www.armory.com/~spectre/ --
 Cameron Kaiser, Point Loma Nazarene University * ckaiser@...
-- TRUE HEADLINE: Prostitutes Appeal to Pope ----------------------------------

Cameron Kaiser | 21 May 17:57 2001

Re: web->gopher


*and* :-) One tiny suggestion -- maybe make it turn "GET /" selectors into
real HTTP URLs?

--

-- 
----------------------------- personal page: http://www.armory.com/~spectre/ --
 Cameron Kaiser, Point Loma Nazarene University * ckaiser@...
-- The older a man gets, the farther he had to walk to school as a boy. -------

em@nuel | 21 May 18:07 2001
Picon

Re: web->gopher


> By the way, I just discovered a mail in my spam-filter from you about some
> problem with the World Gopher list. I fixed it and it seems to work now --
> sorry about that. Typo :-)

Excellent!

> *and* :-) One tiny suggestion -- maybe make it turn "GET /" selectors into
> real HTTP URLs?

I used to do that, but I removed it after deciding that it's contrary to
the spec.  My interpretation is that the 'h' type denotes an HTML
document stored on a gopher server.  According to the spec, selectors
have no meaning.  There's nothing stopping 'GET /whatever.html' from
being a selector for a gopher server, so turning it into an HTTP request
is incorrect.

I create web links by creating an HTML document on the gopher server
that redirects the user to the destination web site.  It works well with
everything.

I don't handle HTML documents correctly yet.  Web->gopher should go
through and re-write all the URLs so that relative links work.

Cameron Kaiser | 21 May 18:14 2001

Re: web->gopher


> > *and* :-) One tiny suggestion -- maybe make it turn "GET /" selectors into
> > real HTTP URLs?
> 
> I used to do that, but I removed it after deciding that it's contrary to
> the spec.  My interpretation is that the 'h' type denotes an HTML
> document stored on a gopher server.  According to the spec, selectors
> have no meaning.  There's nothing stopping 'GET /whatever.html' from
> being a selector for a gopher server, so turning it into an HTTP request
> is incorrect.
> 
> I create web links by creating an HTML document on the gopher server
> that redirects the user to the destination web site.  It works well with
> everything.
> 
> I don't handle HTML documents correctly yet.  Web->gopher should go
> through and re-write all the URLs so that relative links work.

I'll buy your theory -- yeah, my main reason for concern was that images
didn't show up right if they were relative URLs.

One other more practical concern is that some clever d00d might use
heatdeath as an HTTP proxy, which might be a problem if it became
popularised in terms of bandwidth. Using real URLs would not stop this
completely, of course, but it wouldn't make doing it so obvious.

--

-- 
----------------------------- personal page: http://www.armory.com/~spectre/ --
 Cameron Kaiser, Point Loma Nazarene University * ckaiser@...
-- "I'd love to go out with you, but I'm rethreading my toothbrush bristles." -
(Continue reading)


Gmane