Client/server web application architectures for offline usage, data structures, and related methods

• US 20070033569A1
• Filed: 08/02/2005
• Published: 02/08/2007
• Est. Priority Date: 08/02/2005
• Status: Active Grant

• Current Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Original Assignee: AOL Inc. (Apollo Global Management, Inc.)
• Inventors: Ridgeway, James, Landsman, Richard, Davidson, James, Folkman, Nathan
• Granted Patent: US 7,594,003 B2
• Time in Patent Office: Days
• US Class Current: 717/103
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 2463/121 Timestamp
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 63/126 the source of the received data
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• 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/59 Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable

Abstract

Client-server architectures for allowing web applications to operate even when the client and server are disconnected. Exemplary architectures include a local web engine associated with a local cache which can be separate from a browser cache and browser application. Exemplary data structures include web documents having one or more control commands embedded in the head with manifest code. Exemplary methods include operating web applications when the client is offline, caching web applications, executable code, web documents, security code, and/or remote files, allowing web application access of local files, and operating client/web applications.

Claims

1. In a network system having a server that hosts a web-based application for execution on one or more clients, the system configured to allow a client to execute the web-based application locally at the client when the connection between the client and the server is severed, the client comprising:

a control command detecting module configured to detect control commands embedded in transmissions from the server to the client, the control commands instructing the client to cache at least one of a web application, executable code, web document, security code, or remote files;

a caching module configured to store the at least one of a web application, executable code, web documents, security code, or remote files;

a network status module configured to detect when the connection between the client and the server is severed or reconnected; and

a synchronizing module configured to synchronize files stored locally at the client with files stored remotely at the server when the client and server become reconnected.

2. The system as recited in claim 1, wherein the web application or web document is modified from the web application or web document located at the server to include instructions on how to handle requests from the client that require connection to the server.

3. The system as recited in claim 1, wherein the executable code provides the instructions on how to handle requests from the client that require connection to the server.

4. The system as recited in claim 1, wherein the control commands comprise at least one of:

a caching command to cache one or more manifest items in the transmission from the server;

an execution command to execute one or more manifest items in the transmission from the server;

or

a cache behavior command to control a browser cache or another cache existing on the client.

5. The system as recited in claim 4, wherein the transmission from the server manifests the one or more items using at least one of:

embedding the manifest one or more items in the transmission;

or

referring to pathfile on the server at which the one or more manifest items can be access.

6. The system as recited in claim 4, wherein the control command detecting module is further configured to strip the control command and the one or more manifest item from the transmission from the server.

7. The system as recited in claim 1, further comprising:

a browser application that executes the web-application from the server; and

a browser cache.

8. The system as recited in claim 7, wherein the caching module is configured to store the at least one of a web application, executable code, web documents, security code, or remote files in another cache separate from the browser cache.

9. The system as recited in claim 1, further comprising at least one of:

a local file access module for controlling whether an incoming web application or web document allows access to local files stored on the client;

or

a security module for authenticating transmissions between the server and the client or within the client itself.

10. In a network system having a server that hosts a web-based application for execution on one or more clients, the system configured to allow a client to execute the web-based application locally at the client when the connection between the client and the server is severed, the client comprising:

a caching module configured to store at least one of a web application, executable code, security code, or remote files;

a network status module configured to detect when the connection between the client and the server is severed or reconnected; and

a synchronizing module configured to synchronize files stored locally at the client with files stored remotely at the server when the client and server become reconnected.

11. The system as recited in claim 10, wherein the web application is modified from the web application located at the server to include instructions on how to handle requests from the client that require connection to the server.

12. The system as recited in claim 10, wherein the executable code provides the instructions on how to handle requests from the client that require connection to the server.

13. The system as recited in claim 10, further comprising:

a browser application that executes the web-application from the server; and

a browser cache.

14. The system as recited in claim 13, wherein the caching module is configured to store the at least one of a web application, executable code, security code, or remote files in another cache separate from the browser cache.

15. The system as recited in claim 10, further comprising a security module for authenticating transmissions between the server and the client or within the client itself.

16. The system as recited in claim 10, further comprising at least one of:

a polling module for communicating with the server for updates to the web application;

a data tap module for monitoring transmissions between the server and the client;

a search module for performing a remote or local search;

a system status module for monitoring the hardware and software on the client;

a download module for downloading information from the server to the client;

an indexing module for indexing information in a browser cache or another cache; and

a networking module for querying other clients for file sharing.

17. The system as recited in claim 16, further comprising an alert application residing on the client for providing a dialogue box to notify the user of findings of one or more of these modules.

18. The system as recited in claim 10, the caching module further being configured to store local file access code for controlling whether the web application can access local files stored on the client.

19. The system as recited in claim 10, further comprising a search application for searching remote files on the server and searching local files on the client and combining the search results.

20. In a network system, wherein a server hosts a web-based application for execution on a client, the client having a browser application for executing the web-based application, a method for allowing the browser application to execute the web-based application when the client loses communication with the server, the method comprising:

identifying at least one of a web application, executable code, web document, or remote files located in a cache at the client;

detecting when the client loses communication with the server;

redirecting requests from a browser application to the local cache; and

displaying at least one of a web application or web document in the browser application.

21. The method as recited in claim 20, further comprising using the executable code to provide instructions on how to treat requests that require connection to the server.

22. The method as recited in claim 20, wherein the web application or web document includes instructions on how to treat requests that require connection to the server.

23. The method as recited in claim 20, wherein identifying at least one of a web application, executable code, web document, or remote files located in a cache at the client further comprises:

receiving a web document from a server;

identifying a cache command sent with the web document;

storing at least one of a web application, executable code, web document, or remote files at in the cache at the client.

24. The method as recited in claim 20, wherein redirecting requests from a browser application to the local cache comprises sending the requests to at least one of a web application, executable code, web document, or remote files located in local cache.

25. The method as recited in claim 20, further comprising:

maintaining changes occurring in the remote files stored in the local cache;

detecting when the client reestablishes communication with the server; and

synchronizing the changes in the remote files in the local cache with the remote files stored at the server.