Server-originated differential caching

• US 7,269,784 B1
• Filed: 04/04/2001
• Issued: 09/11/2007
• Est. Priority Date: 01/22/2001
• Status: Expired due to Term

• Current Assignee: Digital River Incorporated (Danube Private Holdings II, LLC)
• Original Assignee: Digital River Incorporated (Danube Private Holdings II, LLC)
• Inventors: Mann, Walter, Kasriel, Stephane
• Primary Examiner(s): Hong, Stephen
• Assistant Examiner(s): Stork, Kyle R.
• Application Number:
  US09/827,268
• Time in Patent Office: 2,351 Days
• Field of Search: 715/500, 715/513, 715/517, 715/523, 715/530, 709/311, 709/203
• US Class Current: 715/205
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching

Abstract

The invention provides a method and system for sending relatively identical web pages, when requested by subsequent users, with substantial reduction of bandwidth. The server determines a “template web page” corresponding to the actual information on the web page, and having a set of insertion points, at which changed data can be inserted by the client. The server sends a JavaScript program corresponding to the template web page, which makes reference to the template web page and the changed data, along with sending the actual changed data itself. A first user requesting the web page receives the entire web page, while a second user requesting the web page (or the first user re-requesting the web page at a later time) receives the template information plus only the changed data. The server re-determines the template web page from time to time, such as when a ratio of changed data to template web page data exceeds a selected threshold. The server identifies the particular template web page to the client using a unique identifier (an “E-tag”) for the particular data sent in response to the request. Since the E-tag refers to the template, not the underlying web page, when the standard client makes its conditional request for the web page “if not changed”, the server responds that the web page is “not changed” even if it really is, but embeds the changed data in a cookie it sends to the client with the server response to the client request.

Claims

1. A method for transmitting a web page, comprising steps of:

generating a plurality of template document versions from an original data document at a server, each template document including a set of insertion points, each insertion point including code fragments usable by a client and capable of reading changed data and inserting the read changed data into the template document to render a copy of the original data document at the client;

receiving a request message at the server relating to the original data document, the request message comprising indicia of template document versions in a client local cache; and

sending a response message in response to the request message by selecting one of the plurality of template document versions based on the indicia in the response message and including information identifying the selected template document version in the response message such that the client may utilize the selected template document version in the client local cache along with the changed data to render the copy of the original data document at the client.

2. The method of claim 1 wherein the receiving step comprises receiving the request message formed as an HTTP protocol message and wherein the sending step comprises sending the response message as an HTTP protocol message.

3. The method of claim 1 wherein the receiving step comprises receiving the request message including information identifying at least one template document already available to a sender of the request message in a client local cache.

4. The method of claim 1 wherein the sending step comprises sending the response message including the template document.

5. The method of claim 1 wherein the sending step comprises sending the changed data includes a set of changed data from an earlier version of the original data document.

6. The method of claim 1 wherein the sending step comprises sending the changed data includes a set of personalized data relating to a version of the original data document.

7. The method of claim 1 comprising a step of redefining the template document in response to changes in the original document.

8. The method of claim 7 wherein the redefining step comprises redefining the template document in response to the changed data being larger than a selected fraction of a size of the original data document.

9. The method of claim 1 wherein the code fragments include JavaScript.

10. A method of presenting a web page at the client comprising the steps of claim 1 and further comprising a step of rendering the copy of the original data document at the client by:

(i) parsing the template document, (ii) performing any code fragments, and (iii) inserting any changed data at the set of insertion points in the template document.

11. The method of claim 1 wherein the changed data comprises a cookie.

12. A server apparatus comprising:

a templatization mechanism that generates a plurality of template document versions from an original data document, each template document including a set of insertion points, each insertion point including code fragments usable by a client and capable of reading changed data and inserting the read changed data into the template document to render a copy of the original data document at the client;

a receiver configured to receive a request message from the client relating to the original data document, the request message comprising indicia of template document versions in a client local cache; and

a transmitter configured to send a response message in response to the request message by selecting one of the plurality of template document versions based on the indicia in the response message and including information identifying the selected template document version in the response message such that the client may utilize the selected template document version in the client local cache along with the changed data to render the copy of the original data document at the client.

13. The server apparatus of claim 12 wherein the request message comprises an HTTP protocol message and the response message comprises an HTTP protocol message.

14. The server apparatus of claim 12 wherein the request message includes information identifying at least one template document already available to a sender of the request message in a client local cache.

15. The server apparatus of claim 12 wherein the response message includes the template document.

16. The server apparatus of claim 12 wherein the changed data includes a set of changed data from an earlier version of the original data document.

17. The server apparatus of claim 12 wherein the changed data includes a set of personalized data relating to a version of the original data document.

18. The server apparatus of claim 12 wherein the templatization mechanism is configured to redefine the template document in response to changes in the original document.

19. The server apparatus of claim 18 wherein the templatization mechanism is configured to redefine the template document in response to the changed data being larger than a selected fraction of a size of the original data document.

20. The server apparatus of claim 12 wherein the code fragments include JavaScript.

21. A system comprising the server apparatus of claim 12 and further comprising the client, the client being configured to render the copy of the original data document by:

(i) parsing the template document, (ii) performing any code fragments, and (iii) inserting any changed data at the set of insertion points in the template document.

22. The server apparatus of claim 12 wherein the changed data comprises a cookie.