User configurable prefetch control system for enabling client to prefetch documents from a network server

• US 6,023,726 A
• Filed: 01/20/1998
• Issued: 02/08/2000
• Est. Priority Date: 01/20/1998
• Status: Expired due to Term

• Current Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Original Assignee: Netscape Communications Corporation (Apollo Global Management, Inc.)
• Inventors: Saksena, Gagan
• Primary Examiner(s): VU, VIET DUY
• Application Number:
  US09/009,324
• Time in Patent Office: 749 Days
• Field of Search: 709/201, 709/203, 709/217, 709/218, 709/219, 709/230, 709/231, 709/232, 709/234, 709/250, 709/300, 709/302, 711/137, 711/204, 77/10, 77/104
• US Class Current: 709/219
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A prefetching and control system for a computer network environment. The user configures the client'"'"'s prefetch parameters which are: enabling/disabling prefetching, prefetch threshold value, and the maximum number of documents to prefetch. A prefetch value or weight is contained in the Hypertext Markup Language (HTML) page or prefetch file, called a pathfile, for each link. The HTML page contains the prefetch values for each of its links, while pathfile contains the weights for every link on the HTML page associated with the Universal Resource Locator (URL). The client compares the prefetch or weight values of each link with its threshold value to decide if the link should be prefetched and placed in the local cache as long as the maximum number of documents to prefetch is not exceeded. Pathfiles reside on the server and are created by the server or web administrator/author. The server automatically creates the pathfiles from its log files which are filtered to retain all of the valid document requests and average paths are derived from the filtered results. Weights are assigned to each path in the URL by the server and inserted into the pathfile along with the associated paths. If no log files exist on the server, then the web administrator/author may manually enter in the weights for each path.

Claims

1. A process for prefetching documents in a computer network environment, comprising the steps of:

configuring prefetch parameters of a client;

parsing a document for prefetch values;

comparing said prefetch parameters with said prefetch values; and

prefetching documents from a server onto said client;

wherein said prefetch values determine the relative weight of each link in said document.

2. The process of claim 1, wherein said prefetch parameters include enabling and disabling the prefetch.

3. The process of claim 1, wherein said prefetch parameters include a prefetch threshold value.

4. The process of claim 1, wherein said prefetch parameters include a document prefetch limit, limiting the amount of documents that said client prefetch.

5. The process of claim 1, said parsing step further comprising the steps of:

parsing the Hypertext Markup Language (HTML) document for prefetch values;

requesting a prefetch file from said server if no prefetch values exist in said HTML document and said prefetch file exists on said server and said prefetch file does not exist in the local cache;

receiving said prefetch file on said client;

placing said prefetch file into said local cache; and

parsing said prefetch file for prefetch values;

wherein said HTML document contains prefetch values for each document link in said HTML document; and

wherein said prefetch file contains paths within the HTML page associated with the Universal Resource Locator (URL) and their associated prefetch values.

6. The process of claim 1, said comparing step further comprising the step of:

selecting a link with said prefetch values greater than said prefetch parameters.

7. The process of claim 4, said prefetch step further comprising the steps of:

retrieving a link from said server if said link does not exist in the local cache;

storing said link in said local cache; and

stopping said prefetch process when the number of prefetched documents has reached said document prefetch limit or no more links exist;

wherein said prefetch process is repeated for each qualified link.

8. The process of claim 1, further comprising the step of:

assigning a greater weight to any links in the vicinity of the user'"'"'s mouse position on the computer screen.

9. The process of claim 1, further comprising the steps of:

querying each link in said document for keywords; and

assigning a greater weight to links containing a common keyword.

10. The process of claim 1, further comprising the step of:

assigning a greater weight to links contained in a sequential pattern.

11. The process of claim 1, further comprising the step of:

assigning greater weights to links contained in a hub and spoke pattern.

12. The process of claim 5, wherein said server notifies said client if said prefetch file exists.

13. The process of claim 5, wherein said server includes said prefetch file in a multi-part message.

14. The process of claim 1, wherein said client notifies said server if said client is configured for prefetching.

15. An apparatus for prefetching documents in a computer network environment, comprising:

a module for configuring the prefetch parameters of a client;

a module for parsing a document for prefetch values;

a module for comparing said prefetch parameters with said prefetch values; and

a module for prefetching documents from a server onto said client;

wherein said prefetch values determine the relative weight of each link in said document.

16. The apparatus of claim 15, wherein said prefetch parameters include enabling and disabling the prefetch.

17. The apparatus of claim 15, wherein said prefetch parameters include a prefetch threshold value.

18. The apparatus of claim 15, wherein said prefetch parameters include a document prefetch limit, limiting the amount of documents that said client prefetch.

19. The apparatus of claim 15, said parsing module further comprising:

a module for parsing the Hypertext Markup Language (HTML) document for prefetch values;

a module for requesting a prefetch file from said server if no prefetch values exist in said HTML document and said prefetch file exists on said server and said prefetch file does not exist in the local cache;

a module for receiving said prefetch file on said client;

a module for placing said prefetch file into said local cache; and

a module for parsing said prefetch file for prefetch values;

wherein said HTML document contains prefetch values for each document link in said HTML document; and

wherein said prefetch file contains paths within a Universal Resource Locator (URL) and their associated prefetch values.

20. The apparatus of claim 15, said comparing module further comprising:

a module for selecting a link with said prefetch values greater than said prefetch parameters.

21. The apparatus of claim 18, said prefetch module further comprising:

a module for retrieving a link from said server if said link does not exist in the local cache;

a module for storing said link in said local cache; and

a module for stopping said prefetch module when the number of prefetched documents has reached said document prefetch limit or no more links exist;

wherein said prefetch module is repeated for each qualified link.

22. The apparatus of claim 15, further comprising:

a module for assigning a greater weight to any links in the vicinity of the user'"'"'s mouse position on the computer screen.

23. The apparatus of claim 15, further comprising:

a module for querying each link in said document for keywords; and

a module for assigning a greater weight to links containing a common keyword.

24. The apparatus of claim 15, further comprising:

a module for assigning a greater weight to links contained in a sequential pattern.

25. The apparatus of claim 15, further comprising:

a module for assigning greater weights to links contained in a hub and spoke pattern.

26. The apparatus of claim 19, wherein said server notifies said client if said prefetch file exists.

27. The apparatus of claim 19, wherein said server includes said prefetch file in a multi-part message.

28. The apparatus of claim 15, wherein said client notifies said server if said client is configured for prefetching.