| |
| | RFC 1436 (rfc1436) |
 | | Assume that a "well- known" Gopher server (this may be duplicated, details are discussed Anklesari, McCahill, Lindner, Johnson, Torrey & Alberti [Page 3] RFC 1436 Gopher March 1993 later) listens at a well known port for the campus (much like a domain-name server). |
 | | Examples of such servers include Gopher-to-FTP gateways, Gopher-to- archie gateways, Gopher-to-WAIS gateways, etc. There are a number of Anklesari, McCahill, Lindner, Johnson, Torrey & Alberti [Page 7] RFC 1436 Gopher March 1993 advantages of such mechanisms. |
 | | Anklesari, McCahill, Lindner, Johnson, Torrey & Alberti [Page 8] RFC 1436 Gopher March 1993 All intelligence is carried by the server implementation rather than the protocol. |
| www.cse.ohio-state.edu /cgi-bin/rfc/rfc1436.html (4686 words) |
|