EFFICIENT STATE RECONCILIATION

• US 20120323990A1
• Filed: 06/15/2011
• Published: 12/20/2012
• Est. Priority Date: 06/15/2011
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Hayworth, Christopher Robert
• Application Number:
  US13/161,350
• Publication Number:
  US 20120323990A1
• Time in Patent Office: Days
• US Class Current: 709/203
• 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/55 Push-based network services

Abstract

The embodiments described herein generally relate to methods and systems for using a token as a bi-directional parameter of a long polling request for state updates. A client polls a server for state updates, in which updates may be the result of a server event. Server state data is hashed to generate a token/hash representing the current state data. The server compares this token/hash to the token/hash received from the client in the polling request. If the tokens differ, the server sends the actual state data with the server token to the client. By using tokens as request parameters, unnecessary state updates are avoided, and client/server synchronization is achieved more quickly by restricting the pushing of data to state updates. Further, the client may force a response to a poll by sending an empty or random/default value for the token request parameter.

Claims

1. A computer-implemented method for pushing state data to a client, the method comprising:

receiving a state update at a server;

in response to receiving the state update, altering the state at the server;

hashing the state at the server;

generating a token on the server, wherein the token is the hash of the state;

receiving a token from the client;

determining if the token on the server and the received token from the client differ; and

if the token on the server and the received token from the client differ, pushing state data with the token on the server to the client.

2. The computer-implemented method of claim 1, wherein the determining if the token on, the server and the received token from the client differ comprises determining if a value of the token on the server and a value of the received token from the client differ.

3. The computer-implemented method of claim 1, further comprising:

receiving, from the client, a request for a state update, wherein the received token from the client is a parameter of the request for a state update.

4. The computer-implemented method of claim 3, further comprising:

if the token on the server and the received token from the client do not differ, holding the received request and the received token from the client.

5. The computer-implemented method of claim 3, wherein a value of the received token from the client is empty.

6. The computer-implemented method of claim 5, further comprising:

determining the token on the server and the received empty token value from the client differ; and

pushing state data with the token on the server to the client.

7. The computer-implemented method of claim 5, further comprising:

in response to the empty value, pushing the state data with the token on the server to the client in a predetermined time period.

8. The computer-implemented method of claim 1, wherein the state data pushed to the client comprises the received state update.

9. The computer-implemented method of claim 1, wherein the state update is received from an application comprising a document editing session.

10. One or more computer storage media storing computer-executable instructions that when executed by a processor perform a method for polling a server for state data, the method comprising:

sending, by a client, a first request for the state data at the server, wherein the first request comprises a first token;

receiving the state data with a second token;

comparing the first token and the second token to determine if the received state data differs from state data stored at the client; and

if the first token and the second token differ, updating the state data stored at the client.

11. The one or more computer storage media of claim 10, wherein the polling comprises Hypertext Transfer Protocol (HTTP) long polling via a token mechanism.

12. The one or more computer storage media of claim 10, further comprising:

if the first token and the second token differ, storing the second token at the client.

13. The one or more computer storage media of claim 12, further comprising:

sending a second request for the state data at the server, wherein the second request comprises the second token;

in response to the second request, receiving the state data with a third token;

comparing the second token and the third token to determine if the received state data differs from state data stored at the client; and

if the second token and the third token differ, updating the state data stored at the client.

14. The one or more computer storage media of claim 10, wherein the first token comprises a random value.

15. The one or more computer storage media of claim 14, wherein the random value is passed in the first token to force a response from the server, and wherein the response from the server is received in a predetermined period of time.

16. The one or more computer storage media of claim 10, wherein the received state data comprises one or more state updates.

17. A system for pushing state data at a server to a client via a token mechanism, the system comprising:

a processor; and

memory coupled to the processor, the memory comprising computer program instructions executable by the processor to provide;

a management module within the server, wherein the management module is configured to;

receive a state update;

in response to receiving the state update, alter the state;

hash the state;

generate a token on the server, wherein the token is the hash of the state;

receive a token from the client;

determine if the token on the server and the received token from the client differ; and

if the token on the server and the received token from the client differ, push state data with the token on the server to the client.

18. The system of claim 17, further comprising:

if the token on the server and the received token from the client do not differ, holding the received token from the client.

19. The system of claim 17, wherein the state update is received from an application comprising a document editing session.

20. The system of claim 17, wherein a value of the received token from the client is empty, and wherein, in response to the empty value, the state data is pushed to the client in a predetermined period of time.