home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: alt.gopher
- Path: sparky!uunet!usc!sol.ctr.columbia.edu!eff!news.oc.com!mercury.unt.edu!sol!billy
- From: billy@sol.acs.unt.edu (Billy Barron - VAX/UNIX Systems Manager)
- Subject: Re: index for all of gopherspace
- Message-ID: <1992Jul27.180509.27470@mercury.unt.edu>
- Sender: usenet@mercury.unt.edu (UNT USENet Adminstrator)
- Organization: University of North Texas
- References: <1992Jul27.163746.974@nstn.ns.ca>
- Date: Mon, 27 Jul 1992 18:05:09 GMT
- Lines: 29
-
- daniel@nstn.ns.ca (Daniel MacKay) writes:
-
- >Now, the WAIS thang works because all the people who run WAISs, have sent
- >in to the mother of all WAISs, an abstract for each database they've
- >published.
- >
- Not all. I've found quite a few WAISs that are NOT in the master directory.
- This also is the biggest problem with WAIS. The directory is flat and getting
- too big.
-
- >Here's the problem I'm trying to solve: I know somewhere in gopherspace
- >there's a really good recipe database. But where is it?
- >
- I agree this is a BIG problem. I was going to bring it up at the Gopher
- Developer's Conference in a couple of weeks and see what could be worked
- out.
-
- >You send a query to the meta-database server, and it returns a
- >list of databases. You pick one [or several- but we can't do this without
- >overhauling the client] of those, and your client sends a search off to
- >them.
- >Now, why couldn't we do this with gopher?
- >
- This could be done. Actually, I don't really care to make this a "user"
- feature. It would involve some major coding and maybe a protocol change.
- Just something us sysadmins use to figure out where we would like to place
- links to.
-
-
-