OFFLINE AUTOMATED PROXY CACHE FOR WEB APPLICATIONS

• US 20080098093A1
• Filed: 10/16/2007
• Published: 04/24/2008
• Est. Priority Date: 10/16/2006
• Status: Abandoned Application

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Palm, Inc. (TCL Technology Group Corp.)
• Inventors: Chatterjee, Manjirnath, Simon, Gregory
• Application Number:
  US11/873,305
• Publication Number:
  US 20080098093A1
• Time in Patent Office: Days
• US Class Current: 709/219
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: Y02D 30/00 Reducing energy consumption in communication networks

Abstract

Embodiments of the present invention provide techniques for managing content updates for web-based applications. In one set of embodiments, a configurable proxy cache is provided that executes rule-based content updates of web content on the behalf of an application (e.g., web browser) while the application is not running. This allows for better management of intermittent connection quality, memory/power savings for mobile devices, and caching of information that can be shared with the application and other network-aware applications/services. In various embodiments, the proxy cache is controlled by the application via standard web language constructs such as HTTP headers, thereby enabling interoperability with web-based applications that implement common asynchronous data-loading technologies.

Claims

1. A method for managing content updates for an application, the method comprising:

receiving from the application a first request for data, wherein the first request includes one or more configuration parameters, and wherein the one or more configuration parameters define a schedule for retrieving the data from a remote server; and

retrieving the data from the remote server according to the schedule, wherein the step of retrieving is performed while the application is not running.

2. The method of claim 1, wherein retrieving the data from the remote server according to the schedule comprises:

forwarding, at a time indicated in the schedule, the first request to the remote server;

receiving the data from the remote server in response to the forwarding of the first request; and

storing the data in a cache.

3. The method of claim 2 further comprising:

receiving from the application a second request for the data; and

transmitting the data stored in the cache to the application in response to the second request.

4. The method of claim 2, wherein the one or more configuration parameters include a history parameter defining a maximum number of versions of the data that may be stored in the cache simultaneously.

5. The method of claim 1, wherein the one or more configuration parameters include a time interval parameter defining a time interval at which the data is to be retrieved from the remote server.

6. The method of claim 1, wherein the one or more configuration parameters include a retry parameter defining a number of times to retry a connection to the remote server.

7. The method of claim 1, wherein the one or more configuration parameters include a notification parameter indicating that a notification should be transmitted to the application upon occurrence of an event.

8. The method of claim 7, wherein the event corresponds to a detection of a new email.

9. The method of claim 1, wherein the application is a web browser.

10. The method of claim 1, wherein the first request is an HTTP request, and wherein the one or more configuration parameters correspond to one or more HTTP headers.

11. A method for managing content updates for an application, the method comprising:

receiving from the application a first request for data, wherein the first request includes an identifier that uniquely identifies the first request;

forwarding the first request to a remote server;

receiving the data from the remote server in response to the forwarding the first request;

storing the received data and the unique identifier in a cache;

receiving from the application a second request for the data, wherein the second request includes the identifier;

retrieving the data from the cache using the identifier; and

transmitting the data retrieved from the cache to the application.

12. A configurable proxy comprising:

a request processing component configured to;

receive, from a client application, a request for data; and

detect the presence of one or more proxy configuration parameters within the request;

a rules component configured to;

determine a schedule for retrieving the requested data from a remote server based on the one or more proxy configuration parameters; and

repeatedly forward the request to the remote server according to the determined schedule without further requests from the client application; and

a data storage component configured to cache data received from the remote server for later transmission to the client application.

13. The configurable proxy of claim 12, wherein the request is an HTTP request, and wherein the one or more proxy configuration parameters correspond to one or more HTTP headers.

14. The configurable proxy of claim 12, wherein the configurable proxy is implemented as a software application running on a handheld device.

15. A system for managing content updates, the system comprising:

a first computing device configured to execute a first client application and a first proxy application, the first proxy application being configured to;

receive, from the first client application, a first request for first data, wherein the first request includes one or more configuration parameters, and wherein the one or more configuration parameters define a first schedule for retrieving the first data from a remote server; and

retrieve the first data from the remote server according to the first schedule, wherein the step of retrieving is performed while the first client application is not running.

16. The system of claim 15 further comprising:

a second computing device configured to execute a second client application and a second proxy application, the second proxy application being configured to;

receive, from the second client application, a second request for second data, wherein the second request includes one or more configuration parameters, and wherein the one or more configuration parameters define a second schedule for retrieving the second data from the remote server; and

retrieve the second data from the remote server according to the second schedule, wherein the step of retrieving is performed while the second client application is not running; and

a third computing device communicatively coupled with the first and second computing devices, wherein the third computing device is configured to execute a shared proxy application, and wherein the first and second proxy applications are configured to access the remote server through the shared proxy application.

17. The system of claim 15, wherein retrieving the first data from the remote server according to the first schedule comprises:

forwarding, at a time indicated in the first schedule, the first request to the remote server;

receiving the first data from the remote server in response to the forwarding of the first request; and

storing the first data in a cache.

18. The system of claim 17, wherein the first proxy application is further configured to:

receive a second request for the first data from the first client application; and

transmit the first data stored in the cache to the first client application in response to the second request.

19. The system of claim 15, wherein the first request is an HTTP request, and wherein the one or more configuration parameters correspond to one or more HTTP headers.

20. The system of claim 15, wherein the first computing device is a handheld device.

21. A machine-readable medium for a computer system, the machine-readable medium having stored thereon a series of instructions which, when executed by a processing component, cause the processing component to:

receive from an application a first request for data, wherein the first request includes one or more configuration parameters, and wherein the one or more configuration parameters define a schedule for retrieving the data from a remote server; and

retrieve the data from the remote server according to the schedule, wherein the step of retrieving is performed while the application is not running.

22. The machine-readable medium of claim 21, wherein retrieving the data from the remote server according to the schedule comprises:

forwarding, at a time indicated in the schedule, the first request to the remote server;

receiving the data from the remote server in response to the forwarding of the first request; and

storing the data in a cache.

23. The machine-readable medium of claim 21 further having instructions that cause the processing component to:

receive from the application a second request for the data; and

transmit the data stored in the cache to the application in response to the second request.

24. The machine-readable medium of claim 21, wherein the first request is an HTTP request, and wherein the one or more configuration parameters correspond to one or more HTTP headers.