Architectural pattern for persistent web application design

• US 8,725,793 B2
• Filed: 04/03/2009
• Issued: 05/13/2014
• Est. Priority Date: 04/03/2009
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Kroeger, Robert J., Nicolaou, Alexander, Kobyakov, Pavel V., Kennberg, Aleksandr V.
• Primary Examiner(s): Anwari, Maceeh
• Application Number:
  US12/418,483
• Publication Number:
  US 20100257230A1
• Time in Patent Office: 1,866 Days
• Field of Search: 709/203
• US Class Current: 709/203
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 51/216 Handling conversation history, e.g. grouping of messages in sessions or threads
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• 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/59 Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable

Abstract

A computer system operating a web application with offline capabilities, including a web browser, a local web application, a write queue maintained in the local memory and a persistent local database. When the web application needs to perform an operation on a data item, the web application issues a database request to determine if the data item is in the local database. If the data item is not in the local database, the web application issues the data request to the server system. If the data item is in the local database, the web application performs the operation on the data item stored in the database and writes the operation to the write queue along with the identifier of the data item. When a network connection exits between the client device and the server system, the web interface drains the write queue to the server system.

Claims

1. A client device comprising:

one or more processors;

memory; and

one or more programs, wherein the one or more programs are stored in the memory for execution by the one or more processors, the one or more programs including instructions for;

receiving a request to perform an operation on a respective data item associated with a web application, wherein data items associated with the web application are accessible via a network connection between the client device and a server system;

in response to the request to perform the operation on the respective data item, without regard to an availability of the network connection between the client device and the server system, determining whether the respective data item is stored in a local database in memory of the client device;

sending, to the server system, a request for the respective data item, the sending being responsive to a determination that the respective data item is not stored in the local database; and

performing the operation on the respective data item stored in the local database, the performing being responsive to a determination that the respective data item is stored in the local database.

2. The client device of claim 1, wherein the local database is stored in non-volatile memory.

3. The client device of claim 1, wherein the web application is a web-based email application with offline capabilities.

4. The client device of claim 3, wherein the data items are thread lists or conversations in the email application.

5. The client device of claim 1, wherein when the client device detects that the local database is full, at least some data items in the local database are marked for deletion in accordance with a cache replacement policy.

6. The client device of claim 1, further comprising instructions for:

in accordance with a determination that the operation involves updating the respective data item, writing information characterizing the operation to a write queue for the web application along with the respective identifier of the respective data item so as to enable the operation to also be performed on a copy of the respective data item stored at the server system; and

when a network connection exits between the client device and the server system after performing the operation on the respective data item, draining the write queue to the server system.

7. The client device of claim 6, wherein the write queue includes a plurality of operations for corresponding data items, and draining the write queue includes sending the operations in the write queue to the server system in the order in which they were stored in the write queue.

8. The client device of claim 1, wherein said determining whether the respective data item is in a local database in memory of the client device occurs while the client device has a network connection to the server system.

9. The client device of claim 1, wherein the local database contains a plurality of data items, each data item of the plurality of data items being associated with a corresponding identifier that enables the corresponding data item to be uniquely identified on the client device and on the server system.

10. A method, comprising:

performing by a client device, including one or more processors and memory storing one or more programs, the method comprising the following steps;

receiving a request to perform an operation on a respective data item associated with a web application, wherein data items associated with the web application are accessible via a network connection between the client device and a server system;

in response to the request to perform the operation on the respective data item, without regard to an availability of the network connection between the client device and the server system, determining whether the respective data item is stored in a local database in memory of the client device, sending, to the server system, a request for the respective data item, the sending being responsive to a determination that the respective data item is not stored in the local database; and

performing the operation on the respective data item stored in the local database, the performing being responsive to a determination that the respective data item is stored in the local database.

11. The method of claim 10, wherein the local database is stored in non-volatile memory.

12. The method of claim 10, wherein the web application is a web-based email application with offline capabilities.

13. The method of claim 12, wherein the data items are thread lists or conversations in the email application.

14. The method of claim 10, wherein when the client device detects that the local database is full, at least some data items in the local database are marked for deletion in accordance with a cache replacement policy.

15. The method of claim 10, further comprising:

in accordance with a determination that the operation involves updating the respective data item, writing information characterizing the operation to a write queue for the web application along with the respective identifier of the respective data item so as to enable the operation to also be performed on a copy of the respective data item stored at the server system; and

when a network connection exits between the client device and the server system after performing the operation on the respective data item, draining the write queue to the server system.

16. The method of claim 15, wherein the write queue includes a plurality of operations for corresponding data items, and draining the write queue includes sending the operations in the write queue to the server system in the order in which they were stored in the write queue.

17. The method of claim 10, wherein said determining whether the respective data item is in a local database in memory of the client device occurs while the client device has a network connection to the server system.

18. The method of claim 10, wherein the local database contains a plurality of data items, each data item of the plurality of data items being associated with a corresponding identifier that enables the corresponding data item to be uniquely identified on the client device and on the server system.

19. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a client device with one or more processors, cause the client device to:

receive a request to perform an operation on a respective data item associated with a web application, wherein data items associated with the web application are accessible via a network connection between the client device and a server system;

in response to the request to perform the operation on the respective data item, without regard to an availability of the network connection between the client device and the server system, determine whether the respective data item is stored in a local database in memory of the client device

send, to the server system, a request for the respective data item, the sending being responsive to a determination that the respective data item is not stored in the local database; and

perform the operation on the respective data item stored in the local database, the performing being responsive to a determination that the respective data item is stored in the local database.

20. The computer readable storage medium of claim 19, wherein the local database is stored in non-volatile memory.

21. The computer readable storage medium of claim 19, wherein the web application is a web-based email application with offline capabilities.

22. The computer readable storage medium of claim 21, wherein the data items are thread lists or conversations in the email application.

23. The computer readable storage medium of claim 19, when the client device detects that the local database is full, at least some data items in the local database are marked for deletion in accordance with a cache replacement policy.

24. The computer readable storage medium of claim 19, further comprising instructions to:

in accordance with a determination that the operation involves updating the respective data item, write information characterizing the operation to a write queue for the web application along with the respective identifier of the respective data item so as to enable the operation to also be performed on a copy of the respective data item stored at the server system; and

when a network connection exits between the client device and the server system after performing the operation on the respective data item, drain the write queue to the server system.

25. The computer readable storage medium of claim 24, wherein the write queue includes a plurality of operations for corresponding data items, and draining the write queue includes sending the operations in the write queue to the server system in the order in which they were stored in the write queue.

26. The computer readable storage medium of claim 19, wherein said determining whether the respective data item is in a local database in memory of the client device occurs while the client device has a network connection to the server system.

27. The computer readable storage medium of claim 19, wherein the local database contains a plurality of data items, each data item of the plurality of data items being associated with a corresponding identifier that enables the corresponding data item to be uniquely identified on the client device and on the server system.