System and method for creating pathfiles for use to predict patterns of web surfaces

• US 6,055,572 A
• Filed: 01/20/1998
• Issued: 04/25/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,715
• Time in Patent Office: 826 Days
• Field of Search: 709/201, 709/202, 709/203, 709/217, 709/218, 709/219, 709/223, 709/224, 709/234, 709/300, 707/10, 707/100, 707/104
• US Class Current: 709/224
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching

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 generating pathfiles in a computer network environment, comprising the step of:

creating a pathfile from the server log files;

wherein said pathfile is a prefetch file that contains paths within the HTML page associated with the Universal Resource Locator (URL) and their associated prefetch values; and

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

2. The process of claim 1, said creating step further comprising the step of:

filtering out prefetch requests from said log file.

3. The process of claim 1, said creating step further comprising the step of:

filtering out proxy requests from said log file.

4. The process of claim 1, said creating step further comprising the steps of:

correlating the time gaps between logical document requests in said log file; and

filtering out false correlations from said log file.

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

assigning weights to each link within said URL.

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

inserting said paths, links, and weights into said pathfile.

7. The process of claim 1, wherein said weights are assigned by the user.

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

notifying the client of the location of said pathfile.

9. An apparatus for generating pathfiles in a computer network environment, comprising:

a module for creating a pathfile from the server log files;

wherein said pathfile is a prefetch file that contains paths within a Universal Resource Locator (URL) and their associated prefetch values; and

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

10. The apparatus of claim 9, said creating module further comprising:

a module for filtering out prefetch requests from said log file.

11. The apparatus of claim 9, said creating module further comprising:

a module for filtering out proxy requests from said log file.

12. The apparatus of claim 9, said creating module further comprising:

a module for correlating the time gaps between logical document requests in said log file; and

a module for filtering out false correlations from said log file.

13. The apparatus of claim 9, said creating module further comprising:

a module for assigning weights to each link within said URL.

14. The apparatus of claim 9, said creating module further comprising:

a module for inserting said paths, links, and weights into said pathfile.

15. The apparatus of claim 9, wherein said weights are assigned by the user.

16. The apparatus of claim 9, further comprising:

a module for notifying the client of the location of said pathfile.