home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!sgiblab!darwin.sura.net!jvnc.net!netnews.upenn.edu!msuinfo!pigeon.egr.msu.edu!symanzik
- From: symanzik@pigeon.egr.msu.edu (Edward Symanzik)
- Newsgroups: comp.infosystems.gopher
- Subject: Re: New/additional gopher at the Univ of Utah
- Message-ID: <1992Nov17.165654.7244@msuinfo.cl.msu.edu>
- Date: 17 Nov 92 16:56:54 GMT
- References: <9211131904.AA27868@pyramid> <SKLEPZI.4.0@SSB1.SAFF.UTAH.EDU> <BxpKn8.Bw9@cs.dal.ca> <1992Nov16.220045.13753@msuinfo.cl.msu.edu>
- Sender: news@msuinfo.cl.msu.edu
- Distribution: na
- Organization: College of Engineering, Michigan State University
- Lines: 30
-
- In article <1992Nov16.220045.13753@msuinfo.cl.msu.edu>, boone@convex.cl.msu.edu (Dennis Boone) writes:
-
- |> I'd like to see one listing per {campus,commercial organization,govt. entity}
- |> in the Gopher Central database. I see no reason why that server can't take
- |> on the responsibility of pointing to all gophers at its organization. This
- |> would help the problem some.
-
- An alternate solution would be to do this at the central server.
-
- For instance, instead of:
- 109. University of Michigan CITI/
- 110. University of Michigan GOpherBLUE Service/
- 111. University of Michigan Libraries/
- 112. University of Michigan Medical Center/
-
- Have:
- 109. University of Michigan/
-
- and:
- 1. University of Michigan CITI/
- 2. University of Michigan GOpherBLUE Service/
- 3. University of Michigan Libraries/
- 4. University of Michigan Medical Center/
-
- Just scanning through the list it looks like this would save a couple of pages. Not real impressive, but it's a start.
-
- --
- Ed Symanzik
- Michigan State University
- symanzik@egr.msu.edu
-