Funny Gopher Pop Up R Gif
| Internet protocol suite |
|---|
| Application layer |
|
| Transport layer |
|
| Internet layer |
|
| Link layer |
|
The Gopher protocol ( pron.: / ˈ ɡ oʊ f ər / ) is a TCP/IP awarding layer protocol designed for distributing, searching, and retrieving documents over the Net. Strongly oriented towards a menu-document design, the Gopher protocol presented an culling to the Globe Wide Web in its early stages, but ultimately HTTP became the dominant protocol. The Gopher ecosystem is often regarded as the effective predecessor of the Globe Wide Web.
Invented past a team led past Mark P. McCahill at the University of Minnesota, the protocol offers some features non natively supported past the Web and imposes a much stronger bureaucracy on information stored on it. Its text card interface is piece of cake to use, [ane] and well-suited to computing environments that rely heavily on remote text-oriented computer terminals, which were still common at the time of its creation in 1991, and the simplicity of its protocol facilitated a wide variety of client implementations. More contempo Gopher revisions and graphical clients added support for multimedia. [one] Gopher was preferred past many network administrators for using fewer network resource than Web services. [ii]
With its hierarchical structure, Gopher provided a useful platform for the get-go large-calibration electronic library connections. [3] Gopher users remember the organisation as being "faster and more efficient and so much more organised" than today'south Spider web services. [iv] Although largely supplanted by the Web in the years following, the Gopher protocol is still in use by enthusiasts, and a small population of actively maintained servers remains.
Contents
- 1 Origins
- 2 A New User Feel
- 3 Stagnation
- 3.1 Native Gopher support
- iii.2 Gopher browser plugins
- 3.3 Gopher clients for mobile devices
- 3.4 Other Gopher clients
- iii.v Gopher to HTTP gateways
- iv Technical details
- 4.1 Gopher characteristics
- 4.2 Protocol
- 4.3 Gopher item types
- 4.3.one URL links
- 4.4 Related technology
- five Gopher server software
- half-dozen See too
- 7 References
- eight External links
- eight.1 Standards
Origins
The original Gopher system was released in tardily spring of 1991 by Mark McCahill, Farhad Anklesaria, Paul Lindner, Daniel Torrey, and Bob Alberti of the University of Minnesota. [5] Its central goals were, as stated in RFC 1436:
- A file-similar hierarchical organization that would be familiar to users.
- A elementary syntax.
- A organisation that can exist created quickly and inexpensively.
- Extending the file arrangement metaphor, such as searches.
Gopher combines document hierarchies with collections of services, including WAIS, the Archie and Veronica search engines, and gateways to other data systems such as FTP and Usenet.
The full general interest in Campus-Wide Information Systems (CWISs) [6] in college educational activity at the time, and the ease with which a Gopher server could be ready to create an instant CWIS with links to other sites' online directories and resources were the factors contributing to Gopher's rapid adoption. By 1992, the standard method of locating someone's email address was to find their organization'south CCSO nameserver entry in Gopher, and query the nameserver. [7]
The name was coined by Anklesaria [8] as a play off of several meanings of the word "gopher." The Academy of Minnesota mascot is the gopher, [9] a gofer (aforementioned sound) is an banana who "goes for" things, and a gopher burrows through the ground to reach a desired location.
A New User Experience
Contemporary accounts [10] offer a glimpse of what using Gopher was like when the program burst onto the scene, unified several resource, and created "Gopher space".
On a screen with 25 lines of 80 dark-green characters each (no graphics so, long since remedied) you got a series of hierarchical menus. The tiptop level menu might be all the departments and publications (e.grand., the campus paper) of your academy, which had invested in running a Gopher server as a way of delivering documents electronically, at least to the local community.
There were no search engines as we know them today. Available information was presented in a series of nested menus, intended to resemble a hierarchical file system of folders, something familiar to computer users who saw whatsoever search for data as trying to detect that detail file (document) which held a particular respond.
If you wanted recent news for the women's volleyball team, yous would get to the "Daily Reddish Newspaper" carte item and choose the "Give-and-take Search of Latest Month" detail. When asked to enter a search cord, you lot would enter the word "volleyball." All articles in the local Daily Ruby-red newspaper from the terminal calendar month that contained the give-and-take "volleyball" would be listed as a split carte du jour. You could select which one to get commencement. In function for lack of bandwidth, the organization's presentation was intended to announced equally listings of files, without their content. In that location were no paragraphs from inside the "hits", each with the word "volleyball" in boldface type.
And if you don't know what the newspaper is chosen or even if it is available? Searching a summit level bill of fare chosen "Keyword Search of [all] Gopher Menus" with a keyword "daily" would get you into the Daily Cerise publication yous wanted for your "volleyball" search.
Note that this core Gopher functionality searches one publication in one location only (the campus paper at a local university). Nevertheless, the arrangement was robust and its power soon grew. The sys admins setting up whatever local Gopher server had freedom to change bill of fare hierarchies and names independently of the underlying file systems. What enabled Gopher to requite and so many who worked with it a foretaste of the World Wide Web yet to come was the power to add links to other Gopher servers around the world. Now users could hop from one server to another in "Gopher space" (the start "cloud") without thinking about a single underlying network accost.
True, to actually get the text you wanted, you had to click on several links, and read through a bill of fare each time before you lot choose another link. Yet that worked more than rapidly than people might recollect today, and in the heyday of Gopher, much fourth dimension was spent choosing and organizing links in layouts that could exist grasped at a glance. Gopher became the text-handling, document-delivery system it was intended to be. A user could brandish a text document on her screen, save it to a file, print it out, or fifty-fifty e-mail a copy to another person on the Cyberspace. Gopher became the dominant client for other data services: Broad Area Data Servers (WAIS), FTP, and Archie, a database of the files held by well-nigh of the major anonymous (public) FTP sites on the Internet. Initially, Gopher could search only one WAIS database at a time, and WAIS's "relevance feedback" tool (find content-similar documents) was not bachelor.
The World wide web added graphics to text, only lost the menus. It took a while for increased ability in communication, storage and computation -- bandwidth a grand times broader (9600 baud MODEM to cobweb optics), arrays of disk drives each a thousand times larger (under 1 GB to over one TB) and cheap servers (PC CPUs a thousand times faster) -- to permit u.s.a. to regularly clamber the Web and catalog it for search engines. While Gopher's carte du jour system seems quaint, we should remember the time between the decline in Gopher usage and the inflow of search engine ascendency. Back and so, early Globe Broad Spider web users looked eagerly for lists of links ("my favorite links" pages), and users were anxious to bookmark skillful links that they might never observe again. Without structured menus, users had taken a step backwards, but, with less construction, something with more than generality and much greater ability emerged by the dawn of the 21st century: the World Wide Spider web.
Stagnation
The World wide web was in its infancy in 1991, and Gopher services speedily became established. By the tardily 1990s, Gopher had largely ceased expanding. Several factors contributed to Gopher's stagnation:
- In February 1993, the University of Minnesota announced that it would charge licensing fees for the use of its implementation of the Gopher server. [11] Every bit a consequence of this, some users were concerned that a licensing fee would also exist charged for contained implementations. [12] [xiii] Users were scared abroad from Gopher engineering, to the advantage of the Web, which CERN disclaimed ownership of. [fourteen] In September 2000, the Academy of Minnesota re-licensed its Gopher software under the GNU GPL. [xv] [16]
- Gopher client functionality was quickly duplicated by early Spider web browsers, such as Mosaic, which subsumed the protocol equally part of their functions.
- Gopher has a more than rigid structure compared to the free-course HTML of the Web. With Gopher, every document has a defined format and blazon, and the typical user navigates through a single server-defined card system to go to a particular document. This can exist quite dissimilar from the fashion a typical user might traverse documents on the Spider web.
Gopher remains in active utilize by its enthusiasts -- similar Adam Curry and Dave Winer, the inventors of podcasting -- and there have been attempts to revive the utilize of Gopher on mod platforms and mobile devices. One such attempt is The Overbite Project, which hosts various browser extensions and modern clients.
As of 2012[update], there are approximately 160 gopher servers indexed by Veronica-2, [17] reflecting a boring growth from 2007 when there were fewer than 100, [xviii] although many are infrequently updated. Within these servers Veronica indexed approximately two.v million unique selectors. A handful of new servers are fix every yr by hobbyists – over fifty have been set upward and added to Floodgap's list since 1999. [19] A snapshot of Gopherspace as it was in 2007 was circulated on BitTorrent and is still available. [xx] Due to the simplicity of the Gopher protocol, setting up new servers or adding Gopher support to browsers is often done in a natural language in cheek fashion, principally on April Fools' Day. [21] [22]
Native Gopher back up
| Browser | Currently Supported | Supported from | Supported until | Notes |
|---|---|---|---|---|
| Camino | Yep | 1.0 | current | Always uses port lxx. |
| Classilla | Yes | ix.0 | electric current | Hardcoded to port 70 from ix.0–9.ii; whitelisted ports from 9.2.i. |
| gyre | Yes | 7.21.2 (Oct 2010) | current | cURL is a control-line file transfer utility |
| ELinks | Beta [23] | Build option | ||
| Epiphany | No | 2.26.3 | Disabled later on switch to WebKit | |
| Galeon | Yeah | current | ||
| Google Chrome | No [24] | never | An extension to automatically frontwards to Gopher proxies was available, but needs to be rewritten to work with current versions of Chrome. | |
| Internet Explorer | No | 1 | 6.0 | IE 6 SP1+ and IE with MS02-047 requires registry patch to re-enable. [25] Always uses port seventy. |
| Internet Explorer for Mac (discontinued) | No | v.2.iii | PowerPC-only | |
| K-Meleon | Yep | electric current | ||
| Konqueror | Plugin | kio_gopher | ||
| lftp | Yes | ? | current | lftp is a command-line file transfer program |
| libwww | Yes | 1.0c (December 1992) | current | libwww is an API for internet applications |
| Line Mode Browser | Yeah | 1.1 (January 1992) | current | |
| Lynx | Yes | current | Consummate back up | |
| Mozilla Firefox | Addon | 0 | 3.half-dozen | Always uses port seventy. Congenital-in support dropped from Firefox four.0 onwards; [26] can exist added back with OverbiteFF. |
| Netscape Navigator (discontinued) | Yes | ? | 9.0.0.6 | |
| NetSurf | No | Under development, based on the cURL fetcher. | ||
| OmniWeb | Aye | 5.9.2 (April 2009) | electric current | First WebKit Browser to support Gopher [27] [28] |
| Opera | No | never | Opera 9.0 includes a proxy capability | |
| Pavuk | Yes | ? | electric current | Pavuk is a spider web mirror (recursive download) software |
| Safari | No | never | ||
| SeaMonkey | Addon | i.0 | ii.0.fourteen | Always uses port seventy. Built-in support dropped from SeaMonkey ii.1 onwards; uniform with OverbiteFF. |
Browsers that exercise not natively support Gopher can still access servers using one of the bachelor Gopher to HTTP gateways.
Gopher support was disabled in Internet Explorer versions 5.x and six for Windows in Baronial 2002 by a patch meant to fix a security vulnerability in the browser's Gopher protocol handler to reduce the attack surface which was included in IE6 SP1; however, information technology tin can exist re-enabled by editing the Windows registry. In Internet Explorer seven, Gopher support was removed on the WinINET level. [29]
Gopher browser plugins
For Mozilla Firefox and SeaMonkey, OverbiteFF extends Gopher browsing and supports Firefox 4. Information technology includes back up for accessing Gopher servers not on port 70 using a whitelist and for CSO/ph queries, and allows versions of Firefox and SeaMonkey that practise non support Gopher natively to access Gopher servers. Plugins are likewise bachelor for Konqueror [30] and a proxy-based extension for Google Chrome. [31]
Gopher clients for mobile devices
Some take suggested that the bandwidth-sparing simple interface of Gopher would be a adept match for mobile phones and personal digital assistants (PDAs), [32] merely so far, mobile adaptations of HTML and XML and other simplified content have proven more pop. The PyGopherd server provides a built-in WML front end-end to Gopher sites served with it.
The early 2010s accept seen a renewed interest in native Gopher clients for popular Smartphones. Overbite, an open up source client for Android 1.5+ was released in alpha phase in 2010. [33] PocketGopher was also released in 2010, along with its source code, for several Java ME uniform devices. iGopher was released in 2011 as a proprietary client for iPhone and iPad devices.
Other Gopher clients
Gopher was at its height of popularity during a fourth dimension when there were still many as competing computer architectures and operating systems. As such, at that place are several Gopher clients available for Acorn RISC OS, AmigaOS, Atari MiNT, CMS, DOS, classic Mac OS, MVS, NeXT, OS/2 Warp, about UNIX-like operating systems, VMS, Windows 3.10, and Windows 9x. GopherVR was a client designed for 3D visualization, and at that place is even a Gopher customer MOO object. The majority of these clients are difficult coded to work on TCP port 70.
Gopher to HTTP gateways
Users of Web browsers that take incomplete or no support for Gopher tin can admission content on Gopher servers via a server gateway or proxy server that converts Gopher menus into HTML; known proxies are the Floodgap Public Gopher proxy, Gopher Proxy, and the WikkaGopher proxy. Similarly, certain server packages such as GN and PyGopherd have built-in Gopher to HTTP interfaces. Squid Proxy software gateways whatsoever gopher:// URL to HTTP content, enabling whatsoever browser or web agent to access gopher content easily.
Technical details
The conceptualization of knowledge in "Gopher infinite" or a "cloud" every bit specific data in a particular file, and the prominence of the FTP, influenced the applied science and the resulting functionality of Gopher.
Gopher characteristics
As part of its blueprint goals, Gopher functions and appears much similar a mountable read-only global network file system (and software, such as gopherfs, is available that tin actually mount a Gopher server as a FUSE resource). At a minimum, whatever a person tin practice with data files on a CD-ROM, they can exercise on Gopher.
A Gopher system consists of a series of hierarchical hyperlinkable menus. The option of menu items and titles is controlled by the administrator of the server.
 |  | |
| The top level carte of a Gopher server. Selecting the "Fun and Games" menu item... | ...takes the user to the "Fun and Games" menu. |
Similar to a file on a Spider web server, a file on a Gopher server tin be linked to as a menu item from any other Gopher server. Many servers have advantage of this inter-server linking to provide a directory of other servers that the user tin can admission.
Protocol
The Gopher protocol was first described in RFC 1436. IANA has assigned TCP port 70 to the Gopher protocol.
The protocol is simple to negotiate, making information technology possible to browse without using a client. A standard gopher session may therefore appear as follows:
/Reference1CIA World Factbook /Athenaeum/mirrors/textfiles.com/politics/CIA gopher.quux.org 700Jargon iv.2.0 /Reference/Jargon iv.2.0 gopher.quux.org 70 +1Online Libraries /Reference/Online Libraries gopher.quux.org seventy +1RFCs: Internet Standards /Computers/Standards and Specs/RFC gopher.quux.org 701U.S. Gazetteer /Reference/U.S. Gazetteer gopher.quux.org 70 +iThis file contains information on United States fake (Nil) 0icities, counties, and geographical areas. Information technology has simulated (Nil) 0ilatitude/longitude, population, land and water expanse, fake (NULL) 0iand ZIP codes. fake (Zip) 0i false (Aught) 0iTo search for a city, enter the metropolis's proper name. To search simulated (Aught) 0ifor a county, utilise the name plus Canton -- for example, fake (NULL) 0iDallas Canton. fake (NULL) 0
Here, the client has established a TCP connection with the server on port seventy, the standard gopher port. The client then sends a string followed by a carriage render followed by a line feed (a "CR + LF" sequence). This is the selector, which identifies the document to be retrieved. If the item selector were an empty line, the default directory would be selected. The server and then replies with the requested item and closes the connection. According to the protocol, before the connection is closed, the server should transport a full-stop (i.due east., a period grapheme) on a line past itself. Nevertheless, as is the case here, not all servers conform to this office of the protocol and the server may close the connection without returning the terminal full-finish.
In this example, the item sent dorsum is a gopher carte du jour, a directory consisting of a sequence of lines each of which describes an detail that can be retrieved. Most clients volition display these as hypertext links, and so allow the user to navigate through gopherspace by post-obit the links. [5]
All lines in a gopher menu are terminated by "CR + LF", and consist of five fields: the particular type every bit the very commencement character (see below), the display string (i.e., the description text to display), a selector (i.e., a file-system pathname), host name (i.e., the domain proper noun of the server on which the item resides), and port (i.e., the port number used past that server). The item type and display string are joined without a infinite; the other fields are separated by the tab grapheme.
Because of the simplicity of the Gopher protocol, tools such as netcat make it possible to download Gopher content easily from the command line:
echo jacks/jack.exe | nc gopher.example.org lxx > jack.exe
The protocol is also supported by scroll as of vii.21.2-DEV. [34]
Gopher item types
Detail types are described in gopher menus past a single number or (example specific) letter and act as hints to the client to tell information technology how to handle a specific media blazon in a menu, analogous to a MIME type. Every client necessarily must understand itemtypes 0 and i. All known clients sympathize particular types 0 through 9, g, and south, and all only the very oldest also understand file-types h and i.
- 0 = plain text file
- 1 = directory card listing
- ii = CSO search query
- three = error bulletin
- 4 = BinHex encoded text file
- 5 = binary annal file
- 6 = UUEncoded text file
- 7 = search engine query
- 8 = telnet session arrow
- 9 = binary file
- yard = GIF image
- h = HTML file
- i = informational message
- I = Prototype file of unspecified format. Client decides how to display. Ofttimes used for JPEG images.
- s = Audio file format, primarily a WAV file
- T = tn3270 session pointer
A list of additional file-type definitions has continued to evolve over time, with some clients supporting them and others not. As such, many servers assign the generic ix to every binary file, hoping that the customer'due south calculator will exist able to correctly process the file.
URL links
Historically, to create a link to a Spider web server, "Get /" was used as a pseudo-selector to simulate an HTTP customer asking. John Goerzen created an addition [35] to the Gopher protocol, usually referred to as "URL links", that allows links to whatever protocol that supports URLs. For example, to create a link to http://gopher.quux.org/, the detail blazon is "h", the display string is the title of the link, the item selector is "URL:http://gopher.quux.org/", and the domain and port are that of the originating Gopher server (and then that clients that do not support URL links volition query the server and receive an HTML redirection page).
The master Gopherspace search engine is Veronica. Veronica offers a keyword search of all the public Internet Gopher server carte du jour titles. A Veronica search produces a carte du jour of Gopher items, each of which is a directly pointer to a Gopher data source. Individual Gopher servers may also utilise localized search engines specific to their content such every bit Jughead and Jugtail.
GopherVR is a 3D virtual reality variant of the original Gopher system.
Gopher server software
Because the protocol is piddling to implement in a basic fashion, there are many server packages still bachelor, and some are still maintained.
- Aftershock – written in Java.
- Bucktooth – modern gopher server written in Perl.
- Geomyidae – written in C. MIT X Consortium License.
- GN
- GoFish
- Gophernicus – Linux, BSD License.
- gophrier – An open source gopher server written in C
- GOPHSERV – cross-platform, GPLv3, FreeBASIC.
- Gopher Cannon – Windows (Win32/Win64), freeware, written in .NET 3.5
- Goscher – written in Scheme.
- Grumpy – Linux, GPLv3, written in FreeBASIC.
- mgod
- PyGopherd – modern gopher+ server written in Python.
- PyGS
- Motsognir open-source gopher server
- gopherfs – a gopher filesystem FUSE abstraction
See likewise
- Veronica – the search engine system for the Gopher protocol, an acronym for "Very Easy Rodent-Oriented Net-broad Index to Computer Archives"
- Gopher+ – early proposed extensions to the Gopher protocol
- GopherVR
- Jugtail – an alternative search engine arrangement for the Gopher protocol. Jugtail was formerly known every bit Jughead.
- SDF Public Access Unix System – a not-turn a profit system which provides free Gopher hosting
- Phlog – The gopher version of a blog
- Wide surface area data server – a search engine whose popularity was contemporary with Gopher
References
- ^ a b "Medical Library Handbook". World Wellness Organization- Regional part for the Eastern Mediterranean. pp. 56–64. http://www.emro.who.int/lin/media/pdf/handbook_chap4_8.pdf. [dead link]
- ^ "How Moore's Law saved united states of america from the Gopher web". 12 March 2009. http://www.newscientist.com/blogs/shortsharpscience/2009/03/how-moores-constabulary-saved-the-web.html . Retrieved 20 September 2011.
- ^ Suzan D. McGinnis (2001). Electronic drove management. Routledge. pp. 69–72. ISBN 0-7890-1309-vi. http://books.google.ca/books?id=A1UoH2vGKE8C&pg=PA69.
- ^ Tomi T. Ahonen (2002). chiliad-Profits: Making Money from 3G Services. Wiley. pp. 33–34. ISBN 0-470-84775-i. http://books.google.ca/books?id=bUJGenHGNdQC&pg=PA33.
- ^ a b December, John; Randall, Neil (1994). The Www unleashed. Sams Publishing. p. 20. ISBN ane-57521-040-one.
- ^ "Google Groups archive of bit.listserv.cwis-l word". Google. http://groups.google.com/grouping/flake.listserv.cwis-l/browse_frm/thread/11db689fbe802834/bc8a60ab89926a4b?lnk=st&q=cwis+gopher&rnum=482&hl=en#bc8a60ab89926a4b . Retrieved 27 July 2011.
- ^ "Google Groups archive of comp.infosystems.gopher discussion". Google. http://groups.google.com/group/comp.infosystems.gopher/browse_frm/thread/eef4cfbdbc862afe/9cbc3e3690b8fb4e?lnk=st&q=%22cso+nameserver%22&rnum=nineteen&hl=en#9cbc3e3690b8fb4e . Retrieved 27 July 2011.
- ^ Marking McCahill, Farhad Anklesaria (in English language) (Flash). "Smart Solutions: Internet Gopher". Minneapolis: University of Minnesota Media Mill. Result occurs at ii:40. http://mediamill.cla.umn.edu/mediamill/brandish/69597. McCahill credits Anklesaria with naming Gopher
- ^ "Gophersports.com – Official Web Site of Academy of Minnesota Athletics". http://world wide web.gophersports.com/ . Retrieved 17 Baronial 2010.
- ^ Ward, Lynn (Dec 1992-January 1993). "Exploring the Power of the Internet Gopher". UIUCnet half-dozen (1). http://www.cl.cam.air conditioning.united kingdom/~jac22/books/www/refs/tools/veronica . Retrieved 5Dec2012.
- ^ University of Minnesota Gopher software licensing policy The Minnesota Gopher Team
- ^ JQ Johnson (25 February 1993). "Message from discussion gopher licensing". Google. http://groups.google.com/groups?selm=1mj6cb$6gm@pith.uoregon.edu . Retrieved 27 July 2011.
- ^ Joel Rubin (3 March 1999). "CW from the VOA server folio – rec.radio.shortwave". Google. http://groups.google.com/groups?selm=36e4c2f1.10244576@nntp.best.ix.netcom.com . Retrieved 27 July 2011.
- ^ Johan Söderberg (2007). Hacking Capitalism: The Complimentary and Open Source Software Move. Routledge. p. 25. ISBN 0-415-95543-2.
- ^ gopher://www.michaeleshun.4t.com
- ^ comp.infosystems.gopher: UMN Gopher(d) released under the GPL
- ^ gopher://gopher.floodgap.com/0/v2/vstat
- ^ Kaiser, Cameron (19 March 2007). "Down the Gopher Hole". TidBITS. http://db.tidbits.com/article/8909 . Retrieved 23 March 2007.
- ^ gopher://gopher.floodgap.com/1/new
- ^ "Download A Piece of Net History". The Changelog. 28 April 2010. http://changelog.complete.org/archives/1466-download-a-piece-of-net-history . Retrieved 27 July 2011.
- ^ "Release Notes – OmniWeb 5 – Products". The Omni Group. http://www.omnigroup.com/applications/omniweb/releasenotes/ . Retrieved 27 July 2011.
- ^ gopher://gopher.floodgap.com/1/new "Service note for one April 2009—This isn't a joke server, guys, we've been running for ten years!"
- ^ Fonseca, Jonas (24 December 2004). "elinks-users Denote ELinks-0.10.0 (Thelma)". Linux from scratch. http://linuxfromscratch.org/pipermail/elinks-users/2004-December/000785.html . Retrieved 22 May 2010.
- ^ hotaru.firefly, et al. (two May 2009). "Issue 11345: gopher protocol doesn't work". Google. http://lawmaking.google.com/p/chromium/issues/item?id=11345 . Retrieved 25 July 2011.
- ^ "Microsoft Security Bulletin MS02-047". Microsoft. 28 February 2003. http://www.microsoft.com/technet/security/bulletin/MS02-047.mspx . Retrieved 23 March 2007.
- ^ "Issues 388195 – Remove gopher protocol support for Firefox". https://bugzilla.mozilla.org/show_bug.cgi?id=388195 . Retrieved 15 June 2010.
- ^ "OmniWeb 5.9.2 now includes Gopher support". OmniGroup. 1 Apr 2009. http://web log.omnigroup.com/2009/04/01/for-firsthand-release-omniweb-592-now-includes-gopher-support/ . Retrieved 3 April 2009.
- ^ "A comprehensive list of changes for each version of OmniWeb". OmniGroup. i April 2009. http://www.omnigroup.com/applications/omniweb/releasenotes/ . Retrieved 3 April 2009.
- ^ "Release Notes for Net Explorer seven". Microsoft. 2006. http://msdn2.microsoft.com/en-u.s.a./ie/aa740486.aspx . Retrieved 23 March 2007.
- ^ "kio_gopher – Gopher kioslave". http://kgopher.berlios.de/ . Retrieved 21 August 2010.
- ^ "The Overbite Project". Floodgap. http://gopher.floodgap.com/overbite/ . Retrieved 25 July 2010.
- ^ Lore Sjöberg (12 Apr 2004). "Gopher: Underground Engineering science". Wired News. http://world wide web.wired.com/news/engineering/0,1282,62988,00.html . Retrieved 27 July 2011.
- ^ Paul, Ryan (half dozen July 2010). "Overbite Project brings Gopher protocol to Android". Ars Technica. http://arstechnica.com/open-source/news/2010/07/overbite-projection-brings-gopher-protocol-to-android.ars?utm_source=rss&utm_medium=rss&utm_campaign=rss . Retrieved 25 July 2010.
- ^ "Curl: Re: Gopher patches for cURL (includes test suite)". http://scroll.haxx.se/mail/lib-2010-08/0339.html . Retrieved 25 August 2010.
- ^ Goerzen, John. (gopher) Links to URL.
External links
- List of all public Gopher servers (proxied link)
- Listing of public Gopher server uptimes (gopher link) (HTTP link)
- An announcement of Gopher on the Usenet eight October 1991
- Why is Gopher Nonetheless Relevant? A position statement on Gopher'south survival.
- An article published by the engineering discussion site "Ars Technica", virtually the Gopher community of enthusiasts present
- Sites inspired by gopher: Spencer Hunter's Homepage – Example of a Gopher emulation in HTML, online since 1995. Under the "Virtually this gopher and myself" directory is the writer'southward ain Gopher manifesto, "Why gopher is superior to the Spider web."; A community server for the Collier County, FL (Naples, FL) expanse whose fast spider web interface is inspired by Gopher. It is also an example of a Gopher emulation in HTML
Standards
- IANA Port Number allocations
- RFC 1436 – The Internet Gopher Protocol (a distributed document search and retrieval protocol)
- RFC 1580 – Guide to Network Resource Tools
- RFC 1689 – Networked Information Retrieval: Tools and Groups
- RFC 1727 – A Vision of an Integrated Net Information Service
- RFC 1738 – Uniform Resource Locators (URL)
- RFC 1808 – Relative Compatible Resource Locators
- RFC 2396 – Compatible Resource Identifiers (URI): Generic Syntax
- RFC 4266 – The gopher URI Scheme
| Early web browsers (upwards to 1996) | |
|---|---|
| |
| 1990 |
|
| 1991 |
|
| 1992 |
|
| 1993 |
|
| 1994 |
|
| 1995 |
|
| 1996 |
|
| Related articles |
|
| Gopher | ||||||
|---|---|---|---|---|---|---|
| Agile clients |
| |||||
| Discontinued clients |
| |||||
| Previously supported |
| |||||
| Server software |
| |||||
| Persons |
| |||||
| See also |
| |||||
davidsonthentell93.blogspot.com
Source: https://kelaskaryawan.stmikmj.ac.id/IT/en/3086-2973/Gopher-protocol_2170_kelaskaryawan-stmikmj.html
0 Response to "Funny Gopher Pop Up R Gif"
Postar um comentário