	       Waisgopher  -- A WAIS to Gopher gateway.
	     Paul Lindner <lindner@boombox.micro.umn.edu>
				   
			     March 1992.

Note:  The waisgopher functionality has been folded into the gopherd
server as of version 1.0.  You really don't need this beast, just plop
.src files into your servers gopher data directory.


Intro
-----

Hey, gopher isn't the only cool network text distribution thing in the
world.  Lots of information is contained in databases only searchable
by WAIS software.  The waisgopher gateway allows you to add a WAIS
database into Gopherspace.

It's not quite the prettiest code out there.  But it's much faster
than the little hack that straps gopher to a WWW in Switzerland and
then to WAIS.

So here it is.  I'll be working on it and making improvements given
time. 


Compilation.
------------

You should have recieved three files in your distribution

waisgopher.README   --  What you're reading now
Makefile.gopher     --  A special makefile for waisgopher (do *not*
                        rename this file as "Makefile"!) 
waisgopher.c        --  The actual code

Copy waisgopher.c and Makefile.gopher into the "ui" directory of your
wais-8-b4 distribution i.e.

  % cp waisgopher.c Makefile.gopher $(WAISdir)/ui

Now cd into the directory you just copied the files into. i.e.

  % cd $(WAISdir)/ui

And type the following:

  % make waisgopher -f Makefile.gopher

This will create the executable "waisgopher" in the WAIS bin
directory.

Note:  If you're using the wais-8-b3.1 or wais-8-b3-ses distributions
comment out the function "PrintStatus()" in the waisgopher.c file.

Usage
-----

waisgopher -h <hostname> [-p <port num>]

  -h   specifies the host that's running the gateway.

  -p   specifies the port that this thing is running on.  You usually
       won't need this.  The gateway tries to find out what port it's
       on.


Getting the darn thing running
------------------------------

The waisgopher gateway is typically run from inetd, although it can
also be run from the command line (which isn't of much use as a
gateway really...)  Here's how I set my up on a sun running SunOS
4.1.1.  (your system will probably differ though...)

Let's suppose that we're going to add the lyrics wais database into
gopher.  The first thing we need is the ".src" file for the database
we're interested in.

Once we have that we set up the system files to run the gateway
automatically.

Add an entry to /etc/services:

   waisgopher  4171/tcp

% cd /var/yp; make    # Update the YP databases

Add a nice long line to /etc/inetd.conf

waisgopher	stream tcp nowait lindner /home/mudhoney/lindner/src/wais-8-b4/bin/waisgopher waisgopher -h mudhoney.micro.umn.edu

Okay, now as root do a:

  # kill -HUP {pid of inetd}

Now add a link in your GopherSpace:

  Type=7
  Name=Lyrics Thing
  Path=/home/mudhoney/lindner/wais-sources/lyrics.src
  Host=mudhoney.micro.umn.edu
  Port=4171

Zim alla bing, it's done!  Hooray!

You can then continue to add other wais databases just by changing the path
variable on the links you make.  This requires that you have a client
that can understand newer links, such as the UNIX client distributed
with this package or any version after March 1992.

