Method and system for distributing object update messages in a distributed network system

• US 8,745,638 B1
• Filed: 09/30/2011
• Issued: 06/03/2014
• Est. Priority Date: 10/01/2010
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Adya, Atul, Cooper, Gregory H., Myers, Daniel Sumers, Reumann, John
• Primary Examiner(s): Truong, Lechi
• Application Number:
  US13/251,042
• Time in Patent Office: 977 Days
• Field of Search: 719/318
• US Class Current: 719/318
• CPC Class Codes: H04L 63/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 67/1004 Server selection for load balancing
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions
• CPC Class Codes: H04L 67/5683 Storage of data provided by user terminals, i.e. reverse caching

Abstract

A distributed network system includes at least one server having memory and one or more processors. The server performs the following operations in connection with propagating object updates to respective client devices: receiving a first object update message from an application server, the first object update message including a first object identifier and a first object version; updating an object update record that includes the first object identifier using the first object version, wherein the object update record includes a first client identifier; propagating the first object version from the object update record to a client-object registration record that includes the first client identifier; and sending a second object update message to a first client device associated with the first client identifier, wherein the second object update message includes the first object identifier and the first object version.

Claims

1. A computer-implemented method, comprising:

at a server having memory and one or more processors, managing objects for one or more web-based applications hosted by one or more application servers, including;

receiving an object registration message from a first client device, the object registration message including;

a first client identifier corresponding to the first client device;

a first object identifier corresponding to a first object cached at the first client device; and

a first object version number corresponding to the first object cached at the first client device;

updating a client-object registration table using the first client identifier, the first object identifier, and the first object version number, thereby registering the first client device to receive notifications of updates to the first object;

receiving a first object update message from an application server of the one or more application servers, the first object update message including the first object identifier and a second object version number;

updating an object update table using a blind write to specify the second object version number as a current version of the first object;

identifying one or more client identifiers in the client-object registration table corresponding to client devices that are registered to receive update notifications for changes to the first object, wherein the one or more client identifiers includes the first client identifier; and

when transmission criteria are met;

sending a second object update message to the first client device, wherein the second object update message includes the first object identifier and the second object version number;

receiving an object update confirmation message from the first client device, the object update confirmation message including a client-cached object version number; and

updating the client-object registration table using the client-cached object version number.

2. The method of claim 1, wherein the client-cached object version number is greater than the second object version number.

3. The method of claim 1, further comprising:

receiving an object registration message from a second client device, the object registration message including;

a second client identifier corresponding to the second client device;

the first object identifier; and

a client-cached object version number corresponding to the first object cached at the second client device; and

updating the client-object registration table using the second client identifier, the first object identifier, and the client-cached object version number, thereby registering the second client device to receive notifications of updates to the first object.

4. The method of claim 1, further comprising:

re-sending the second object update message to the first client device when no object update confirmation message is returned from the first client device within a predefined period of time.

5. The method of claim 4, further comprising repeating the re-sending of the second object update message to the first client device until:

receiving an object update confirmation message from the first client device;

or

reaching a predefined limit on the number of re-sending attempts.

6. The method of claim 1, further comprising:

receiving a request for object updates from the first client device, the request including the first client identifier and one or more object identifiers;

updating the client-object registration table with blind writes using the first client identifier and the one or more object identifiers, thereby registering the first client device to receive notifications of updates to objects corresponding to the one or more object identifiers; and

sending a third object update message to the first client device, the third object update message including the one or more object identifiers and their associated current object version numbers stored at the server.

7. The method of claim 1, further comprising:

receiving a request for object updates to the first object, wherein the request is from the first client device; and

sending a third object update message to the first client device, wherein the third object update message includes the first object identifier and its associated current object version number stored at the server.

8. The method of claim 7, wherein the current object version number associated with the first object identifier is different from the second object version number.

9. The method of claim 1, further comprising:

after updating the object update table,

sending an object update confirmation message to the application server, the object update confirmation message including the first object identifier and the second object version number.

10. The method of claim 1, further comprising:

after receiving the first object update message;

receiving a third object update message from the application server, the third object update message including the first object identifier and a third object version number;

updating the object update table using a blind write to specify the third object version number as a version of the first object;

when the third object version number is less than the second object version number, sending out no object update messages to client devices; and

when the third object version number is greater than the second object version number, sending object update messages for the first object identifier and third object version number to a plurality of client devices, including the first client device.

11. The method of claim 1, wherein the first object is selected from the group consisting of a web-based calendar, a browser bookmark, an address book, and a set of email messages associated with a user.

12. The method of claim 1, wherein the transmission criteria include a determination that the first client device is online.

13. The method of claim 12, wherein the determination that the first client device is online includes receipt of a heartbeat signal from the first client device during a preceding predefined span of time.

14. The method of claim 1, wherein the transmission criteria include a determination that the second object version number is greater than the first object version number.

15. The method of claim 1, wherein there are no transmission criteria to meet as a perquisite of sending the second object message.

16. A server system for managing objects for one or more web-based applications hosted by one or more application servers, comprising:

one or more processors for executing programs; and

memory storing data and one or more programs executable by the one or more processors, the one or more programs including instructions for;

receiving an object registration message from a first client device, the object registration message including;

a first client identifier corresponding to the first client device;

a first object identifier corresponding to a first object cached at the first client device; and

a first object version number corresponding to the first object cached at the first client device;

updating a client-object registration table using the first client identifier, the first object identifier, and the first object version number, thereby registering the first client device to receive notifications of updates to the first object;

receiving a first object update message from an application server of the one or more application servers, the first object update message including the first object identifier and a second object version number;

updating an object update table using a blind write to specify the second object version number as a current version of the first object;

identifying one or more client identifiers in the client-object registration table corresponding to client devices that are registered to receive update notifications for changes to the first object, wherein the one or more client identifiers includes the first client identifier; and

when transmission criteria are met;

sending a second object update message to the first client device, wherein the second object update message includes the first object identifier and the second object version number;

receiving an object update confirmation message from the first client device, the object update confirmation message including a client-cached object version number; and

updating the client-object registration table using the client-cached object version number.

17. A non-transitory computer readable-storage medium storing one or more programs for execution by one or more processors of a server system for managing objects for one or more web-based applications hosted by one or more application servers, the one or more programs comprising instructions for:

receiving an object registration message from a first client device, the object registration message including;

a first client identifier corresponding to the first client device;

a first object identifier corresponding to a first object cached at the first client device; and

a first object version number corresponding to the first object cached at the first client device;

updating a client-object registration table using the first client identifier, the first object identifier, and the first object version number, thereby registering the first client device to receive notifications of updates to the first object;

receiving a first object update message from an application server of the one or more application servers, the first object update message including the first object identifier and a second object version number;

updating an object update table using a blind write to specify the second object version number as a current version of the first object;

identifying one or more client identifiers in the client-object registration table corresponding to client devices that are registered to receive update notifications for changes to the first object, wherein the one or more client identifiers includes the first client identifier; and

when transmission criteria are met;

sending a second object update message to the first client device, wherein the second object update message includes the first object identifier and the second object version number;

receiving an object update confirmation message from the first client device, the object update confirmation message including a client-cached object version number; and

updating the client-object registration table using the client-cached object version number.