Gopherspace
_______________________________________________
|UCNS Computer Review |
|University Computing and Networking Services |
|University of Georgia |
|Computer Services Annex |
|Athens, Georgia 30602 |
|E-Mail: BITNET helpdesk@uga |
| Internet helpdesk@uga.cc.uga.edu |
|_______________________________________________|
Newsletter: Fall Quarter 1993
Author: Albert DeSimone, Jr.
-------------------------------------------------------------
Assembling and utilizing the creative and technical energy to
conceive of and develop the Internet Gopher must have been an
exciting and challenging task for the University of
Minnesota's Internet Gopher Development Team. But with the
popularity of Gopher throughout the world, the team members
can certainly be proud of their efforts.
Gopher is information discovery/retrieval software currently
in use at the University of Georgia. You can use a Gopher
client (software that runs on CMS and CONTAC, DOS, Macintosh,
Unix, etc.) to connect to the UGA Gopher server and find out
what's for lunch at Bolton or Snelling, check out campus
events, connect to the UGA Libraries Online Catalog, search
and browse the UGA Policies and Procedures Manual, and check
out the Athens weather. And this is only the beginning.
Employing the computers and networks on the worldwide
Internet, you can navigate through UGA's slice of Gopherspace
to Gopher servers through the world.
The client/server protocol
Based on the client/server model, the Gopher client presents
you with a menued hierarchy of information items. The menu
and associated items are delivered to the client from a
Gopher server, a repository for the information you receive.
You can then select items from a menu to retrieve a specific
piece of information or a directory of related items.
How you select, retrieve, and search the items presented to
you by the server will depend on the client you are using.
This is truly the essence of a client/server protocol--a set
of rules which allows different computers and operating
systems to communicate with one another. A DOS client,
Macintosh client, Unix client, or CMS client all receive the
same information. The client, however, displays the
information items in a fashion suitable to the environment in
which the client resides. As an example, let's look at how a
graphical user interface on a Macintosh compares to a textual
user interface on CMS and CONTAC
(Figure 1).
Figure 1
The UGA Gopher Server Main Menu
As Presented by a Macintosh client
-------------------------------------------------------------
| File Edit Gopher Setup Recent |
||||||||||||||||||||| Home Gopher Server 1 |||||||||||||||
| Internet Gopher 1991-1993 University of Minnesota |
| |
| About the University of Georgia Gopher |
| Library |
| UGA Campus-Wide Information |
| UGA Departments |
| University System of Georgia |
| Weather |
| Worldwide Information |
| |
| |
| <== xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ==>|
-------------------------------------------------------------
Figure 1
The UGA Gopher Server Main Menu
As Presented by a CMS client
-------------------------------------------------------------
Rice CMS Gopher 2.4.1
GOPHER.UGA.EDU
1/7
(root menu)