JP2004513405A - System, method and program for ordered and pre-caching linked files in a client / server network - Google Patents

Abstract

A system and method for reducing delays associated with browsing linked documents, such as web pages, using a network, such as the Internet.
A system and method for transferring information using a client / server network transmits link popularity information from a server to a client that describes a popularity characteristic of a file linked to a requested file. be able to. This popularity may include the relative likelihood of a user request for each of the linked files. This link popularity information can be used in selecting only more popular link files for advance caching. The file corresponding to the link that the user is most likely to select may be loaded into the server's cache memory and / or downloaded to the client prior to the user selecting any of the links. Ordering files for preemptive caching based on popularity may increase the probability that, at the time a link is selected, the file corresponding to the selected link is already stored on the client computer. Thus, the time between the user selecting a link and viewing the corresponding file is reduced. The time and resources required to perform caching were also required because the most popular linked files are cached first, but the less popular files cannot be selected at all for advanced caching. Reduced compared to pre-caching all files linked to the file.
[Selection diagram] Fig. 1

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to the transfer of information over a network of communication devices, and more particularly, to the ordered advance caching of files linked to a requested file over a network.
[0002]
[Prior art]
Powerful and convenient computing devices have been continually becoming popular with the increasing use of networks connecting them. Computer devices include computers and other devices that are often portable, such as wireless telephones, personal digital assistants, and vehicle-based computers. Such portable computing devices are sometimes referred to as "pervasive devices." The term "computer" as used herein may refer to any such computing device. The network connecting the computer devices may be a "wired" network formed using "terrestrial lines" such as copper or fiber optic cables, a wireless network using terrestrial and / or satellite based wireless transmission links, or , A combination of wired and wireless network portions. Many networks are configured using a client / server architecture, where a "server" computing device allocates resources, such as files, peripherals, or processing power, that may be required by the "client" computing device. to manage. The client device may be operated by a user of the network. Computer devices that are not directly operated by the user, such as a "proxy server" that runs on behalf of another machine, can operate as both a client and a server.
[0003]
Currently, the most widely used network is the Internet, a global network of computer devices that communicate using a collection of protocols called TCP / IP (Transmission Control Protocol / Internet Protocol). One aspect of the Internet that is particularly widespread is the World Wide Web (WWW or "web"), a collection of documents formatted and linked in the hypertext markup language (HTML). These documents or "web pages" may incorporate text, graphic, audio, and / or video content, and may contain useful links to each other, often referred to as "hyperlinks" or simply "links". it can. The document or file is requested by the client computer via an application program called a web browser. This file is requested from the server computer or "web server". A separate Internet protocol called Hypertext Transfer Protocol (HTTP) is used for file transmission. A user viewing a web page on a computer display screen typically "clicks" on the hyperlink using a pointing device, and then the linked document is transferred to the user's computer and displayed.
[0004]
However, the file corresponding to the link selected by the user may not be immediately displayed on the user's display screen. This link file is typically stored on a storage device such as a hard drive associated with the web server. Therefore, this file must typically be retrieved from its storage and then transferred to the user's computer via the Internet. The time required for this retrieval and transfer can cause a noticeable (and sometimes very unpleasant) delay between selecting the link and viewing the associated file or document. Some web servers can partially alleviate this problem by storing the requested file in cache memory for a period of time after the request for the file. The term cache memory, as used herein, refers to memory that allows for fast access to stored items. Usually, the cache memory is a part of the system memory allocated for short-term storage of frequently used information. The files in the cache memory can be transmitted without the delays associated with retrieving the files from long-term storage, so they have recently been requested (possibly by another user) and remain in the cache. The delay experienced by a user requesting a file between selecting the corresponding link and viewing the file may be less. Such caching of a file after a file request can be performed, for example, by a proxy server that transmits web documents between the web server and multiple users. Such proxy servers are often used, for example, by large Internet service providers or ISPs. Although this type of caching can reduce the delay associated with viewing a particular document, the probability that the file corresponding to the link selected by a particular user is in cache memory is not always high.
[0005]
Another technique that can reduce the delay associated with browsing linked files is sometimes referred to as "advanced caching." In advanced caching, a file linked to the requested file (by a hyperlink) is moved to the web server cache memory before the user requests any of the linked files, and / or Downloaded to the client computer. A typical web page has multiple linked documents, but many of the corresponding links may not be selected by a viewer of the web page. Thus, caching and / or downloading all of the linked documents is time consuming and requires resources of the server and client computers (eg, cache memory space) and resources of the network (transmission bandwidth). And needlessly. Unnecessary load on the network transmission capability generally increases the transmission delay in the entire network.
[0006]
[Problems to be solved by the invention]
Accordingly, it is desirable to develop systems and methods that reduce the delay associated with browsing linked documents, such as web pages, using a network, such as the Internet. A desirable approach would be to minimize the waste of time and resources while reducing the delay associated with browsing most of the selected links.
[0007]
[Means for Solving the Problems]
Some of the issues outlined above are addressed in large part by systems and methods for transferring link popularity information between network servers and network clients. This link popularity information describes the popularity characteristics of the file linked to the requested file. This popularity may include the relative likelihood of the user's request for each of the linked files. Link popularity information can be generated in a variety of ways, including analyzing server log files, tracking "hits" on various web pages or visiting various web pages, Or it may involve the analysis of information content such as "cookies" that the client can send to the server. The transfer of link popularity information from the server to the client can also be done in various ways. For example, this information can be stored in a separate file that is sent to the client along with the requested file. Link popularity information can also be incorporated into protocols such as the HTTP protocol and used to send the requested file. Further, link popularity information may be included in the requested file itself, such as, for example, in code (eg, HTML) used to define a link to the link file.
[0008]
This link popularity information can be used in selecting only more popular link files for advance caching. The file corresponding to the link most likely to be selected by the user may be loaded into the server's cache memory and / or downloaded to the client's computing device before the user selects at least one link. it can. This ordering of files for preemptive caching based on popularity may increase the probability that, at the time a link is selected, the file corresponding to the selected link is already stored on the client's computer. Thus, the time between selecting a link by the user and viewing the corresponding file (sometimes referred to as "wait time") is dramatically reduced. The time and resources required to perform caching were also required because the most popular linked files are cached first, but the less popular files cannot be selected at all for advanced caching. Reduced compared to pre-caching all files linked to the file.
[0009]
In one embodiment of the method, the link popularity information is transferred from the server to the client at about the same time that the requested file containing the link corresponding to the popularity information is transferred to the client. Then, at least one of the link files may be transferred from the server to the client, but the link files are transferred in an order determined using the link popularity information. In a preferred embodiment, such a transfer of the link file is a client-initiated download. When the user selects a link in the original requested document that corresponds to one of the link files, the link file can be displayed on the user's display screen (typically on the client's computing device). Display screen).
[0010]
One embodiment of a system for transferring information in a client / server network includes the step of requesting if the network server is further configured to provide link popularity information associated with the requested file to clients of the network. A network server configured to provide the generated files to clients of the network. A server in the network may include a processor, a cache memory, a storage device such as a hard drive, and a connection for transmission media. The requested file and any additional files linked to the requested file are typically stored on storage. The system may further include a client of the network if the client is configured to download one or more additional link files from a server before a user requests any of the link files. Can be. The order in which such link files are downloaded is determined using the link popularity information. Clients are typically configured to download additional files using a web browser. The web browser can be configured to allow a user to select whether advance caching is enabled.
[0011]
In addition to the above methods and systems, the present invention also contemplates computer-usable carrier media. The carrier medium may be a storage medium such as a magnetic disk or an optical disk, a magnetic tape, or a memory. Further, the carrier medium may be a wire, cable or wireless medium through which data or program instructions are transmitted, or a signal carrying data or program instructions over such a wire, cable or wireless medium. The carrier medium may include program instructions executable to perform embodiments of the methods described herein.
[0012]
The invention will now be described, by way of example only, with reference to the accompanying drawings.
[0013]
BEST MODE FOR CARRYING OUT THE INVENTION
Referring now to the drawings, FIG. 1 illustrates one embodiment of a system 10 for transferring information within a client / server network. System 10 includes a network server 12, a computing device that may be a web server. In the embodiment of FIG. 1, server 12 includes cache 14, processor 16, and storage device 18. The cache 14 is a set of storage areas that can be accessed at high speed by the processor 16. In one embodiment, cache 14 may be part of the processor's system memory allocated to temporary information storage. The storage device or storage medium 18 may take many forms, such as volatile or non-volatile memory, magnetic disks such as hard disks or floppy disks, optical disks, and / or magnetic tapes. Such storage is sometimes referred to as "direct access storage" (DASD). Typically, storage device 18 has a larger storage capacity than cache 14, but it takes longer for processor 16 to access it.
[0014]
In the embodiment of FIG. 1, the storage device 18 contains files 20 and program instructions 22, which are also said to be program executable. Program instructions are typically stored in "executable files" in the storage device and loaded into memory during execution. File 20 may include documents, such as web pages, suitable for viewing by users of the network, and may include text, graphics, video and / or audio information. Such a document file may be in the form of HTML language or other suitable language, such as Extensible Markup Language (XML) or Wireless Markup Language (WML). File 20 may further include a data file suitable for use by the computing device when communicating over a network. For example, a file that includes link popularity information for additional files linked to a particular file can be included in file 20. As used herein, the term "file" may refer to any collection of data suitable for storage on a computing device or for transporting over a network. Program instructions 22 may include various program instructions used to implement the functions of network server 12, such as those used to implement the methods described herein.
[0015]
Transmission medium 24 can be used to connect network server 12 to other computing devices, such as proxy server 26 and / or client 28. Transmission medium 24 may include, for example, electrical wires, cables, wireless transmission paths, or combinations thereof. Protocols used for transmission over the transmission medium 24 may include TCP / IP, HTTP, and / or other suitable protocols such as Wireless Application Protocol (WAP).
[0016]
The system 10 may include a client 28 linked to the server 12 using a transmission medium 24. In the embodiment of FIG. 1, client 28 includes cache 14, processor 16, and storage device 35. The storage device 35 is the same storage device 18 as described above, and can include a file 39, a browser program 37, and program instructions 36. Browser programs, such as browser 37, are implemented using program instructions (or executable instructions), such as instructions 36, but in FIG. 1, browser 37 is shown separately to emphasize this functionality of the client. is there. The browser program 37 may be, for example, a web browser that allows a user to retrieve a file on the WWW and browse it, or a program that performs a similar function on another network. In some embodiments, client functionality required for implementation of the methods described herein is included in browser 37. Such functions and / or other functions of the client computing device may also be implemented in separate program instructions, such as program instructions 36. File 39 may include various files stored on the client computing device, including files downloaded from a network server, such as server 12. The client 28 is typically associated with an output device 38 and an input device 40, especially in embodiments where the client's computing device is operated by a user of the system 10. Output device 38 may include, for example, a display screen and / or a printer. The input device 40 may include a pointing device such as a keyboard and / or a mouse, for example.
[0017]
In some embodiments, system 10 may include a proxy server 26. As used herein, the term proxy server refers to a computing device that acts as an intermediary between a client and a "real" server. A proxy server may appear to the client as a server, but to a real server it may appear as a client. Requests from clients can be returned by the proxy server or passed to the real server. Files or other communication information from the real server can be passed to the client by the proxy server. A proxy server may be utilized in system 10 for a variety of reasons. For example, a proxy server can be used to provide dedicated content and / or improved performance to a group of selected client computers. This example may be the use of caching by a proxy server to increase the speed at which a subscriber can serve certain files to a particular ISP. Another use of a proxy server may be to filter information being sent from the client to the real server and / or vice versa. For example, a proxy server can be used to implement a "firewall" at an enterprise or other organization that restricts external access to computers. In the embodiment of FIG. 1, proxy server 26 may include cache 14, processor 16, and storage device 30. Storage device 30 may include file 32 and proxy server program instructions 34. File 32 may include any file stored on the proxy server, such as a file being transmitted between the server and the client. Program instructions 34 may include various program instructions used to implement the functions of proxy server 26, such as interacting with a client computer.
[0018]
In FIG. 1 and all other block diagrams attached herein, blocks are intended to represent a function, rather than a particular structure. Embodiments of the illustrated system using circuitry and / or software may incorporate multiple blocks into a single circuit or single device, or implement multiple circuits and / or multiple You may need to combine the devices. For example, cache 14 may be included on a semiconductor chip that embodies processor 16. Further, systems such as system 10 may include other elements not explicitly shown. For example, multiple servers, proxy servers, and / or clients not shown in FIG. 1 may be included in a system used to implement the methods described herein. Further, the server, proxy server, and / or client computing device may incorporate other elements not shown.
[0019]
An exemplary collection of link popularity information 41 that can be used in implementing the methods described herein is shown in FIG. Requested file 42 may be a file requested by a user (e.g., via a web browser) and thus requested by a client to a server. In the data of FIG. 2, the requested file is an HTML file called "corporationx.html". Link file 44 is a file that is linked into corresponding requested file 42. In the embodiment of FIG. 2, the requested file “corporationx.html” includes links to seven linked files, including “products.html” and “address.html”. In embodiments where the requested file 42 is an HTML file, a link to the link file 44 may be included within the requested file 42 using HTML format tags that define the link. Each of the link files 44 is associated with a corresponding popularity indicator 46. In the embodiment of FIG. 2, each of the popularity indicators 46 is expressed as a probability that a user selecting a link in the requested file 42 will select its corresponding link file. In this example, the indicators for all of the linked files sum to one, so forty percent of the link selections from “corporationx.html” could be the selection of the link corresponding to “products.html”. is there. However, the popularity indicator 46 can be represented in various other forms. For example, the percentage of link selection for selecting the corresponding file can be described for each file, or the percentage of browsing the file selected by the user who has selected the corresponding link can be used. As another alternative, it is possible to provide the actual number of links selected during a period of time or, if possible, the selectivity.
[0020]
In view of the link popularity information of FIG. 2, the server containing the requested file 42 and the link file 44 (typically in a storage device, such as the device 18 of FIG. 1) may request the file "corporationx" When transferring the ".html" to the client, the link files "products.html" and "support.html" can also be loaded into a cache memory on the server, such as the cache 14 of FIG. If either of these linked files is subsequently requested by the client, the files can be quickly transferred to the client without the delay associated with reading the file from storage. Link popularity information 41 may also be made available to clients. In view of the link popularity information, the client can download, for example, the link files “products.html” and “support.html” from the server before the user selects at least one link file. In this way, if either of these link files is selected by the user, the file will already be on the client's computer and the delay associated with transmission between the server and the client will be eliminated. become. The link popularity information 41 indicates that about 70 percent of the link selections are for either “products.html” or “support.html”, so caching and / or downloading these two files Doing so should reduce the latency for about 70 percent of link selections from “corporationx.html”. This performance improvement can be achieved without having to use additional time or resources by caching and / or downloading other less popular linked files.
[0021]
Determining the popularity indicator 46 to form the link popularity information 41 can be accomplished in various ways. For example, a tracking program can be used to represent the number of times a particular file stored by a web server is accessed. Typically, several implementations of such tracking programs are currently commercially available that provide additional information such as which particular user is accessing the file. In some embodiments, identifying "cookies," or information that can be sent to a web server by a web browser, can be used to track the selection of a particular linked file. Another way to determine the popularity of a linked file is to analyze a server log, or a file that contains a record of activity on the server. Web servers typically maintain such log files, including each request made to the server. In another alternative, link popularity information may be estimated based on knowledge about the nature of the link, for example. In some embodiments, such estimates can be used as initial or default settings for link popularity information that can be updated later based on, for example, server statistics or log file analysis. In some embodiments, updates of link popularity information may be performed periodically, possibly with other updates or maintenance associated with the server.
[0022]
Link popularity information, such as the information 41 shown in tabular form in FIG. 2, can be stored on the server and transferred to the client in a number of different ways. In one embodiment, information similar to the information shown in FIG. 2 can be stored in a separate file that can be stored on a server on a device such as the storage device 18 of FIG. Such a file may have the name "corporationx_linkpopularity.html" in the embodiment of FIG. 2 and may be transferred to the client at the same time that the requested file ("corporationx.html") is transferred. . The file may include a variety of programming languages and may convey information using any of a plurality of data structures (eg, a tabular structure or an object-oriented structure). Alternatively, link popularity information may be included in the requested file itself, such as in the formatting used to set each link to the linked file. In such an embodiment, the client's browser program is preferably configured to extract link popularity information from the requested file. Link popularity information may also be included in the header for the requested file, ie, the beginning of the file, typically reserved for information about the file. As another example, link popularity information may be transmitted from a server to a client using a communication protocol such as HTTP (eg, in its header information). In some embodiments, implementations of the method for transmitting link popularity information may require extending the specification of a programming language (such as HTML) or a communication protocol (such as HTTP). The rapid development of computer-based networks usually results in frequent expansions and upgrades to such specifications.
[0023]
The link popularity information shown in FIG. 2 is merely illustrative of one embodiment, and many other embodiments are possible and anticipated. For example, the data of FIG. 2 may include additional possible requested files 42 along with corresponding link files and popularity indicators. In fact, any of the link files 44 shown in FIG. 2 could be included to include the link file itself as one of the requested files 42. The link popularity information may be configured in a format different from that shown in FIG. For example, the requested file may be represented as an object in an object-oriented programming approach, and the link file and corresponding popularity indicator may be represented as attributes of such an object. Further, other issues not explicitly shown in FIG. 2 can be included in the link popularity information. For example, in addition to characterizing the likelihood that a link file will be selected for viewing, the link option may also indicate, for example, the likelihood that the link will be selected first.
[0024]
Referring to FIG. 3, a flow diagram illustrating one embodiment of a method for transmitting information in a client / server network is shown. The method of FIG. 3 can be implemented by a server, such as server 12 of FIG. 1, and can be implemented using program instructions, such as instructions 22. In the embodiment of FIG. 3, after a request for a file stored on the server is received from the client (box 48), link popularity information for the requested file is compiled or located (box 48). 50). The client requesting the file may be, for example, the client 28 of FIG. 1 or a proxy server, for example, the proxy server 26 of FIG. In some embodiments, the link popularity information is already stored on the server when the request for the file is received. As described above in the description of FIG. 2, the link popularity information may be included, for example, in a separate file or in the requested file itself. By using the link popularity information already stored, the server can respond faster to requests for files. Alternatively, link popularity information may, in some embodiments, be compiled in response to a file request, thus providing up-to-date popularity information. In another possible embodiment, the link popularity information for the requested file may be updated at the time of the request by accessing a separate file that contains the periodically updated link popularity information. Such a method is particularly useful in embodiments where the link popularity information is transmitted in the requested file itself, or where the link popularity information is transmitted via a communication protocol.
[0025]
The requested file is transmitted to the requesting computing device (box 52), and link popularity information is also transmitted (box 54). As noted above, link popularity information may be sent in a variety of ways, including as a file in the requested file and / or in transmission protocol commands or headers. In the embodiment of FIG. 3, one or more link files are loaded into a cache memory on the server depending on the relative popularity of the link files (box 56). Various criteria can be used to determine how many files to cache, but in some embodiments, the user (typically a server administrator) can change the criteria. . For example, linked files may be cached using the cached files in a popular order until enough files are cached so that a predetermined percentage of link selections may match. Using the exemplary information of FIG. 2, once the criteria are set to indicate that enough files are to be cached to match 70 percent of the possible link selections from the cached file, "products. html "and" support.html "will be sufficient. However, if using the cached file indicates that 75 percent of the possible link selections should match, then "stockholder.html" will also be cached. Many other types of criteria can be used, such as caching the three most popular files or caching files in popularity order until a predetermined time has elapsed. If the files have the same probability as being selected by the user, other types of link popularity information may be used for use in determining the order of caching. For example, link popularity information may include, in some embodiments, the probability that a file is initially selected, in addition to the probability that all files will be selected. Cached files are typically removed from the cache after some predetermined period of time (or overwritten with other information).
[0026]
In the embodiment of FIG. 3, one or more cached linked files are sent to the client (box 58). This is typically performed in response to a request from the client, which allows the client to cache the most popular linked files in preparation for a user request for such a file. If the link file itself contains a link to another file, the sequence of steps 48-58 can be performed on the requested link file. This can consume excessive time and resources in some cases, but specifically when it is not known whether the link corresponding to the requested link file is actually selected by the user. Can occur. Thus, in some embodiments, a request for a file from a client includes information about whether the file is due to a user's request or whether it is a request for advance caching (prior to any user's request). Can be. In one such embodiment, the server may be configured to transmit link popularity information only for files requested by the user.
[0027]
Many variations of the method of FIG. 3 are feasible and anticipated. For example, if the requested file does not contain any links, the steps for link files will of course be skipped. We believe that the method described herein can reduce the time and resources used in providing advance caching as compared to a method of caching all linked files. These methods also have some cost in terms of time and resources, but in some cases, a user may wish to disable ordered preemptive caching. Disabling caching may be appropriate, for example, if there is a risk of interfering with another application that can take advantage of caching. Such disabling may be implemented, for example, using an option in a browser program. In one such embodiment, a request for a file from a client may include, for example, an instruction not to send link popularity information. In such a case, steps 50 and 54 to 58 can be omitted. Some steps may be performed in a different order than that shown in FIG. For example, the order of steps 50 and 52, as well as the order of steps 54 and 56, can be reversed in some embodiments.
[0028]
A flow chart illustrating another embodiment of a method for transmitting information in a client / server network is shown in FIG. The method of FIG. 4 may be implemented by a client, such as client 28 of FIG. 1, or by a computer acting as a client, such as a proxy server. This method is typically implemented on the client using a browser program, such as browser 37 of FIG. 1, but some or all of the method may be performed by other programs, such as instructions 36 or proxy server instructions 34. It can also be implemented using instructions. In the embodiment of FIG. 4, the file is requested from the server (or possibly a proxy server) in response to the user's selection of the file (box 60). As described above in the description of FIG. 3, such a request to the server may, in some embodiments, include a notification that the request is in response to a user's selection (a request for a file for advanced caching) As opposed to). The request may also include other information in some embodiments, such as a notification that link popularity information will not be provided (in one embodiment where ordered prior caching is disabled by the user). The requested file is received from the server (box 62), and in one embodiment where ordered prior caching is not disabled, link popularity information for any linked files in the requested file is also received (box 64). . The requested file is displayed on the user's display screen (box 66).
[0029]
Based on the received link popularity information, one or more link files associated with the requested file may be requested from the server for advance download (box 68). The criteria used to determine how many linked files are required for the server to download are, as described above in the description of FIG. It may be the same criterion used for selection. The requested link file can then be received from the server and stored in the client computer's cache memory (box 70). If the next file requested by the user (eg, by selecting a link) is one of the cached linked files ("yes" branch of decision box 72), the requested file Can be displayed quickly (box 74). If the requested file is not one of the cached linked files (72 "no" branch), the file is requested to the server (box 60). If the new requested file has a linked file in itself, steps 62 to 70 can be repeated for the new requested file. Several variants of the method of FIG. 4 are feasible and anticipated. As with the method of FIG. 3, steps relating to a linked file, for example, are omitted in embodiments where the requested file does not contain any links, or where ordered prior caching is disabled by the user. be able to. Some of the steps in FIG. 4 can be performed in a different order without detracting from the benefits of the method. For example, the order of steps 62, 64, and 66 can be changed in some embodiments.
[0030]
Program instructions, such as the instructions 22, 34 or 36 of FIG. 1, or instructions in a browser 37 for implementing the method as shown in FIGS. 3 and 4, may be transmitted by or stored on a carrier medium. it can. The carrier medium may be a transmission medium, such as a wire, cable, or wireless transmission link, or a signal conveyed via a wire, cable, or link. The carrier medium may be a storage device such as a volatile or non-volatile memory (eg, a read-only memory or a random access memory), a magnetic disk or an optical disk, or a storage medium such as a magnetic tape.
[Brief description of the drawings]
FIG.
1 is a block diagram illustrating one embodiment of a system for transferring information within a client / server network.
FIG. 2
FIG. 4 illustrates exemplary link popularity data for links in a file accessible using a client / server network.
FIG. 3
5 is a flowchart illustrating one embodiment of a method that can be performed by a server for transferring information within a client / server network.
FIG. 4
4 is a flowchart illustrating one embodiment of a method that can be performed by a client for transferring information within a client / server network.

Claims (61)

A method of transferring information between a network server and a network client, comprising:
Transferring the requested file from the server to the client; and transferring link popularity information associated with the requested file from the server to the client, wherein the link popularity information is transmitted to the client. A method of characterizing the relative likelihood of a user requesting access to each of a plurality of additional files linked to the file. The method of claim 1, wherein transferring the requested file comprises transferring a file of a web page. The method of claim 1, wherein transferring the requested file comprises transferring a marked language document. The method of claim 1, wherein transferring the link popularity information comprises embedding the link popularity information in the requested file. Transferring at least one of the plurality of additional files from the server to the client, wherein the additional files are transferred in an order determined using the link popularity information; The method of claim 1, further comprising transferring the additional file before the user requests any of the following. 6. The method of claim 5, wherein transferring the at least one additional file comprises transferring the at least one additional file to a cache memory associated with the client. 6. The method of claim 5, further comprising loading the at least one of the additional files into a cache memory associated with the server before transferring the at least one of the additional files. The method of claim 5, further comprising displaying one or more of the additional files in response to a user request. The method of claim 1, further comprising compiling the link popularity information before transferring the link popularity information. 10. The method of claim 9, wherein compiling the link popularity information comprises analyzing a log file of a server. The method of claim 5, wherein the transferring at least one of the plurality of additional files is performed in response to a request from the client to the server. The transfer of at least one of the plurality of additional files is performed in response to a request from the client to the server, and the cache memory associated with the at least one of the additional files. 8. The method of claim 7, wherein the loading is performed before the client makes the request to the server. A method for obtaining information using a client / server network, comprising:
Receiving the requested file from the network server;
Receiving link popularity information from the network server, wherein the link popularity information indicates a relative likelihood that a user will require access to each of a plurality of additional files linked to the requested file. Describe features,
Downloading at least one of the plurality of additional files to memory, wherein the at least one of the additional files is downloaded in an order determined using the link popularity information; Is performed before the user makes a request for the additional file,
A method comprising displaying one or more of the additional downloaded files in response to a user request. 14. The method of claim 13, wherein receiving the link popularity information comprises receiving a file containing the link popularity information. 14. The method of claim 13, wherein receiving the link popularity information comprises receiving information transmitted using a transmission protocol header. 14. The method of claim 13, wherein receiving the link popularity information comprises receiving information embedded in the requested file. A system for transferring information within a client / server network, comprising:
A network server configured to provide a requested file to a network client, the network server providing link popularity information associated with the requested file to the network client. The system further configured, wherein the link popularity information describes a relative likelihood characteristic that a user requests access to each of a plurality of additional files linked to the requested file. The system of claim 17, wherein the network server comprises a computing device. 19. The system according to claim 18, wherein said computing device comprises a computer, a telephone, or a personal digital assistant. The system of claim 17, wherein the network server includes a processor, cache memory, storage, and transmission media connection. The claim file and the plurality of linked additional files are stored on the storage device, and the additional files are linked to the file using links embedded within the file. 21. The system according to 20. 22. The system of claim 21, wherein the requested file comprises a web page file and the link comprises a hyperlink. Further comprising the network client, wherein the network client is configured to download one or more of the additional files from the network server before a user requests the one or more files. 18. The system of claim 17, wherein the order of downloading the one or more additional files is determined using the link popularity information. 24. The system of claim 23, wherein said network client comprises a computing device. The system of claim 24, wherein the computing device comprises a computer, a telephone, or a personal digital assistant. 24. The system of claim 23, wherein the network client includes a proxy device through which information is transmitted between the network server and additional network clients. 24. The system of claim 23, wherein said network client comprises a web browser program. 28. The system of claim 27, wherein the web browser program is configured to enable the additional link file to be downloaded before a user's request is blocked by a user. A computer-usable carrier medium,
A first program instruction executable on the computing device for transferring link popularity information associated with a requested file from a computing device to a client computing device, wherein the link popularity information comprises: A carrier medium containing first program instructions that characterize the relative likelihood of a user requesting access to each of a plurality of additional files linked to a linked file. 30. The carrier medium of claim 29, further comprising a second program instruction executable on the computer device for transferring the requested file from the computer device to the client computer device. Third program instructions executable on the computing device for transferring at least one of the plurality of additional files from the computing device to the client computing device, wherein the third program instructions are executable on the computing device. 31. The carrier medium of claim 30, wherein a file includes third program instructions that are transferred in an order determined using the link popularity information. 32. The carrier of claim 31, further comprising a fourth program instruction executable to compile the link popularity information. A computer-usable carrier medium,
First program instructions executable on a computing device for receiving the requested file from the computing device of the server;
A second program instruction executable on the computing device for receiving link popularity information from the server computing device, wherein the link popularity information comprises a plurality of additional linked files linked to the requested file. Second program instructions describing characteristics of the relative likelihood that the user requires access to each of the files;
And a third program instruction executable on the computing device for downloading at least one of the plurality of additional files from the computing device of the server to a memory of the computing device. And
Computer usage wherein the at least one additional file is downloaded in an order determined using the link popularity information, and wherein the downloading is performed before a user makes a request for the additional file. Possible transport medium. 34. The carrier medium of claim 33, further comprising fourth program instructions executable on the computing device for displaying one or more of the downloaded additional files in response to a user request. A method of transferring information between a network server and a network client, comprising:
Transferring the requested file from the server to the client;
Transferring one or more of a plurality of additional files linked to the requested file from the server to the client, wherein the additional files include link popularity information associated with the requested file. And the link popularity information characterizes the relative likelihood that a user will request access to each of a plurality of additional files linked to the requested file. A method that includes: 36. The method of claim 35, further comprising loading the one or more additional files into a cache memory associated with the server before transferring the one or more of the plurality of additional files. Method. 36. The method of claim 35, wherein the transferring one or more of the plurality of additional files is performed prior to any user request for the additional files. The method of claim 35, wherein the transferring one or more of the plurality of additional files is performed in response to a request from the client to the server. 36. The method of claim 35, further comprising compiling the link popularity information prior to the transferring one or more of the plurality of additional files. A method of transferring information between a network server and a network client, comprising:
Transferring the requested file from the server to the client;
Loading one or more of a plurality of additional files linked to the requested file into a cache memory associated with the server, wherein the additional file is associated with the requested file. Loaded in an order determined using the link popularity information, the link popularity information indicates a relative likelihood characteristic that the user requires access to each of a plurality of additional files linked to the requested file. A method that includes writing. 41. The method of claim 40, wherein the loading is performed on the plurality of additional files prior to any request from the client to the server. 41. The method of claim 40, further comprising compiling the link popularity information prior to the loading. A method for obtaining information using a client / server network, comprising:
Receiving the requested file from the network server;
Downloading at least one of a plurality of additional files linked to the requested file to memory, wherein the at least one additional file includes link popularity information associated with the requested file. The method, wherein the link popularity information is downloaded in an order determined using the method, wherein the link popularity information describes characteristics of a relative likelihood that a user requests access to each of a plurality of additional files. 44. The method of claim 43, wherein the downloading is performed before a user makes a request for the additional file. 44. The method of claim 43, further comprising displaying one or more of the downloaded additional files in response to a user request. The method of claim 43, further comprising receiving the link popularity information from the network server before the downloading. The method of claim 46, wherein the receiving the link popularity information comprises receiving a file containing the information. 47. The method of claim 46, wherein the receiving the link popularity information comprises receiving information transmitted using a transmission protocol header. 47. The method of claim 46, wherein the receiving of the link popularity information comprises receiving information embedded in the requested file. A system for transferring information within a client / server network, comprising:
A network server,
Files stored on the network server;
Means for associating link popularity information with the file.
A system wherein the link popularity information characterizes a relative likelihood that a user requires access to each of a plurality of additional files linked to the file. 51. The system of claim 50, wherein the associating means includes an additional file containing the link popularity information. The system of claim 50, wherein the associating means comprises a network communication protocol. A cache memory in the network server;
Means for loading one or more of a plurality of additional files into said cache memory in an order determined using said link popularity information. 54. The method of claim 53, wherein said means for loading comprises means for loading said one or more of a plurality of additional files into said cache memory prior to any request from a network client for said additional files. System. Means for transmitting the file to a network client;
Means for transmitting one or more of the plurality of additional files to the network client, wherein the one or more of the plurality of additional files are in an order determined using the link popularity information. 51. The system of claim 50, further comprising: means for transmitting. The means for transmitting the file includes means for transmitting the file in response to a request from the client, wherein the means for transmitting one or more of the plurality of additional files comprises a request from the client. 56. The system of claim 55, including means for transmitting the one or more additional files in response to a request. The system of claim 55, further comprising the network client. A first program instruction executable on a computing device for transferring one or more of a plurality of additional files linked to a requested file to a client computing device, wherein the additional file is Transmitted in a determined order using link popularity information associated with the requested file, wherein the link popularity information indicates a relative likelihood that a user will require access to each of the plurality of additional files. A computer-usable carrier medium containing first program instructions describing features. Prior to the transfer of the one or more additional files, further comprising second program instructions executable on the computing device for transferring the requested file to the client computing device. Item 59. The transport medium according to Item 58. 59. The carrier medium of claim 58, wherein the first program instructions are further executable to transfer the one or more additional files prior to a user request for the additional files. Executable to load the one or more additional files into a cache memory in an order determined using the link popularity information before the transferring the one or more additional files. 59. The carrier medium of claim 58, further comprising a second program instruction.

Images