Indefinite caching expiration techniques

• US 20080027982A1
• Filed: 07/27/2006
• Published: 01/31/2008
• Est. Priority Date: 07/27/2006
• Status: Abandoned Application

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: eBay Inc.
• Inventors: Early, Justin Christopher, Yao, Yitao, Subramanian, Mahesh, Yang, Connie Y., Bruck, Scott, Goldberg, Arnold J.
• Application Number:
  US11/495,906
• Publication Number:
  US 20080027982A1
• Time in Patent Office: Days
• US Class Current: 707/103X
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching

Abstract

Techniques are presented for indefinite caching expiration techniques. A browser page includes a reference to an object. A client browser acquires a version of the browser page on each access attempt by the client to a site associated with the browser page. The browser acquires or downloads the object (along with perhaps a maximum value for the expiration header equivalent to an indefinite expiry) into client cache via the reference on a first access attempt of the browser page and subsequently does not re-request the object from the site; rather, when the object changes the browser page is updated with a new name for the object thereby forcing the browser to re-request and re-acquire the object on demand and just when the object is modified.

Claims

1. A method, including:

publishing content via a browser page, wherein the content includes a reference to an object accessible from the browser page by activation of the reference; and

periodically updating the browser page by changing an original name to the reference when the object is modified and thereby forcing cache associated with a browser of an accessing client to automatically reacquire the modified object since the original name changed within the browser page.

2. The system of claim 1 further including, setting an initial cache expiration for the object to be a maximum permissible period for the browser of the client when the browser first acquires the browser page.

3. The system of claim 1 further including, conforming to a policy when changing the original name to a new name, wherein the policy makes the new name a derivative of the original name.

4. The system of claim 3, wherein conforming further includes including major release and minor release reference numbers in both the original name and the new name pursuant to the policy.

5. The system of claim 1 further including representing the object as at least one of a style sheet, a script, a video clip, an audio snippet, a graphic, and an image.

6. The system of claim 1, wherein publishing further includes hosting the browser page on a World-Wide Web (WWW) site or portal that is accessible over the Internet to the browser of the client, and wherein the browser reacquires the browser page with each reference to the WWW site.

23. A machine readable medium embodying instructions that, when executed by a machine, cause the machine to perform to claim 1.

7. A method, including:

managing access to a service via a browser page having embedded references to one or more objects, which are initially acquired by browsers of clients by activation of the embedded references and then cached by the browsers for subsequent use by the clients; and

updating the browser page to include new names to the one or more objects when the one or more objects are modified thereby forcing the browsers to reacquire the modified one or more objects when the clients access the browser page, since the new names appear to the browsers to be different objects and different from what was cached.

8. The system of claim 7, wherein managing further includes setting caching attributes associated with the one or more objects to a maximum or indefinite period when the browsers initially active the embedded references and cache the one or more objects.

9. The system of claim 7, wherein updating further includes incrementing numbers appended to original names for the one or more objects when changing the original names to the new names.

10. The system of claim 9, wherein updating further includes incrementing hierarchical component numbers associated with the original names for the one or more objects when changing the original names to the new names and when the modifications to the one or more objects reflect major releases for the one or more objects.

11. The system of claim 7 further including, representing original names associated with the one or more objects and the new names in a format that conforms to a policy associated with versioning of the one or more objects.

12. The system of claim 7 further including, using the browser page as a front-end or entry into a network-based auction service, which is the service, and the one or more objects represent functions of the network-based auction service defined as scripts or style sheets within the browser page.

13. A system, including:

an object; and

a release manager, wherein the object includes a first name associated with an initial release of the object and the first name is accessible to a browser of a client via an embedded reference to a location of the object and the embedded reference is included in a browser page with other references that is to be managed by the release manager, and wherein the release manager changes the first name to a second name within the browser page when the object is modified thereby forcing the browser of the client to reacquire the modified object when the browser page is accessed by the client.

14. The system of claim 13 further including, a name policy that is enforced by the release manager and provides a naming convention for the release manager to generate the second name from the first name.

15. The system of claim 13, wherein the release manager is set a header associated with the object to include a maximum period or indefinite period for caching that is to be used by the browser of the client thereby forcing the browser to never ask for updates to the object and to cache the object initially and once.

16. The system of claim 13, wherein the object is at least one of a script, a style sheet, a video clip, an audio snippet, a graphic, and an image.

17. The system of claim 13, wherein the release manager publishes the second name within a new version of the browser page on a World-Wide Web (WWW) site accessible to the browser of the client over the Internet.

18. The system of claim 17, wherein the browser of the client is to reacquire the browser page from the WWW site on each access attempt by the client.

19. The method of claim 18, wherein the browser of the client is to cache the object with the first name upon an initial access to the browser page and is to not request an update from the release manager on subsequent accesses to the browser page.

20. A system, including:

a browser page; and

a object versioning means, wherein the browser page includes embedded references to one or more objects having first names and the object versioning means renames the first names to second names within the browser page when the one or more objects are modified thereby forcing browsers of clients on access to the browser page to reacquire the one or more objects on demand and when the one or more objects have been modified.

21. The system of claim 20 further including, an object naming means to interface with the object versioning means for purposes of generating the second names from the first names.

22. The system of claim 20, wherein the object versioning means is to initially set caching attributes for the one or more objects to include an indefinite or maximum period for which the browsers are to request a new version of the objects from the object versioning means.