Berners-Lee, T., Masinter, L., and McCahill, M. RFC 1738: Uniform resource locators (URL), December 1994.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....HOW QUICKLY ARCHIVAL INFORMATION BECOMES OUTDATED. WEB REFERENCES Decay FAILURES By Diomidis Spinellis PHOTOGRAPHS BY MICHAEL KLOSE form Resource Locators. URLs are a subset of the Uniform Resource Identifiers (URIs) that provide an abstract identification of a resource location [3]. In general, URLs consist of a scheme (such as http, ftp, or mailto) followed by a colon and a scheme specific part. The syntax of the scheme specific part can vary according to the scheme. However, URL schemes that involve direct use of an IP based protocol to an Internet host use the following ....

Berners-Lee, T., Masinter, L., and McCahill, M. RFC 1738: Uniform resource locators (URL), December 1994.

....We do not require any a priori knowledge about which objects exist, the object request rates, or the peer up probabilities. We now suppose that each object can be identified by a name. There are a number of current projects and research efforts in the direction of assigning names to objects [1, 14]. 12 For example, each object can be identified by a URL or have a unique URN. Object naming is beyond the scope of this paper. We also suppose that each peer has a persistent name, which is assigned when the peer initially subscribes to the application. Because peers typically change their IP ....

....is what we call two argument hashing. This substrate, inspired from CARP [17, 21] uses a hash function that is a function of both (i) the object names, and (ii) the peer names. Specifically, let h(i, j) be a hash function that maps the object name j and the peer name i into the hash space [0, 1]. For example, g( could be a hash function that maps arbitrary ASCII strings into [0, 1] and h(i, j) could be h(i,j) g(i j) where i j is the concatenation of i and j (assuming that both object names and peer names are ASCII strings) We require that the mapping be uniformly dis 13 ....

[Article contains additional citation context not shown here]

T. Berners-Lee, L. Masinter, and M. McCahill. RFC1738: Uniform Resource Locators (URL), December 1994. 24

....distributed system. The WWW enables clients to retrieve hyperlinked content. Names: Web content names are drawn from an infinite space of globally unique Uniform Resource Locators (URLs) which are structured as a fully qualified domain name (FQDN) combined with a locally unique relative URL [1, 4]. The right to bind an FQDN to an IP address is controlled by hierarchical delegation, and the right to bind relative URLs is controlled by local policy. Addresses: WWW addresses are globally unique, hierarchically organized IP addresses of Internet hosts (servers, clients, caches, or ....

T. Berners-Lee, L. Masinter, and M. McCahill. RFC 1738 - Uniform Resource Locators (URL), December 1994.

....by a grant from the NLnet Foundation. vrije Universiteit Department of Mathematics and Computer Science 1 Introduction Resource in the WWW are named using a Uniform Resource Identifiers (URIs) 4] In the current Web, the most common and well known form of URI is Uniform Resource Locator (URL) [5]. A URL is used in the WWW for two distinct purposes: 1) to identify and (2) to access these resources. Combining these two uses, unfortunately, leads to scalability problems, since resource identification has different requirements than resource access. For instance, if we want to replicate a ....

T. Berners-Lee, L. Masinter, and M. McCahill. RFC 1738: Uniform Resource Locators (URL), Dec. 1994.

....a local disk cache to store objects it has retrieved. The disk cache is described in Section 4.6.6 Several example Gatherers are provided with the Harvest software distribution (see Appendix C) 4. 2 Basic setup To run a basic Gatherer, you need only list the Uniform Resource Locators (URLs) [2, 3] from which it will gather indexing information. This list is specified in the Gatherer configuration file, along with other optional information such as the Gatherer s name and the directory in which it resides (see Section 4.6.1 for details on the optional information) Below is an example ....

....bits set. So, for directories, symbolic links and CGI scripts, the HTTP server is always contacted rather than the local file system interface. Lastly, the Gatherer does not perform any URL syntax translations for local mappings. If your URL has characters that should be escaped (as in RFC 1738 [3]) then the local mapping will fail. Note that if your network is highly congested, it may actually be faster to gather via HTTP FTP Gopher than via NFS, because NFS becomes very inefficient in highly congested situations. Even better would be to run local Gatherers on the hosts where the disks ....

[Article contains additional citation context not shown here]

T. Berners-Lee, L. Masinter, and M. McCahill. RFC 1738: Uniform Resource Locators (URL). CERN, December 1994. IETF URI Working Group. Available from ftp://ftp.internic.net/rfc/- rfc1738.txt.

....of the area following the ACM Computing Classification System [Ass98] 20 Diomidis Spinellis and Dimitris Gritzalis Other relevant TEKNO items This entry contains list of other relevant TEKNO items with links to their respective entries. Entry link The entry link is a hypertext URL [BLMM94] link to the entry material. Reviewer The reviewer entry contains where applicable the name of the entry s reviewer(s) Currently a prototype of TEKNO has been implemented in order to verify the viability of the database schema, the user interface, and the population dynamics. It is ....

T. Berners-Lee, L. Masinter, and M. McCahill. RFC 1738: Uniform Resource Locators (URL), December 1994.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC