RESOURCE TRACKING

• US 20130111069A1
• Filed: 12/10/2012
• Published: 05/02/2013
• Est. Priority Date: 10/06/2008
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Gbadegesin, Abolade, Mody, Viraj B., Copeland, Bruce W., Adya, Atul, Kleinpeter, Thomas W., Steere, David C., Zintel, Willaim Michael
• Granted Patent: US 9,413,588 B2
• Time in Patent Office: Days
• US Class Current: 709/248
• CPC Class Codes: G06F 16/24568 Data stream processing; Continuous queries
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

Clients may subscribe to resources for the purpose of receiving notifications of changes in the resource (e.g., a file is added to a shared folder). Storing subscriptions within persistent storage provides data security in the event of a service failure, at the cost of high latency in accessing subscription data. An efficient method for tracking a resource is provided herein. A subscription service creates subscriptions and monitors resources for a client. Upon a subscribed resource change, a notification service stores a notification of the change into a queue associated with the client. Efficient resource tracking is achieved because notification and subscription data is stored in low latency soft memory. The notification service is configured to detect a failure in the notification service and/or subscription service. In the event a service fails, the client provides a recovery mechanism by resubscribing to resources with which the client has an interest.

Claims

1. A system, comprising:

one or more processing units; and

memory comprising instructions that when executed by at least some of the one or more processing units, perform a method comprising;

detecting a change to data, the data comprised in a server;

storing, in soft memory, an indication of at least one of the change or a subscription, by a client, corresponding to the change;

providing a notification of the change to the client;

receiving a request, associated with the change, from the client; and

responsive to receiving the request, providing for synchronization between the server and the client, the synchronization corresponding to at least the change.

2. The system of claim 1, the soft memory comprising volatile memory.

3. The system of claim 1, the providing a notification comprising:

providing, from a subscription service, an indication of the change to a notification service.

4. The system of claim 3, the notification service configured to create one or more queues and the subscription service configured to instruct the notification service into which queue of the one or more queues to store the indication of the change.

5. The system of claim 1, the method comprising:

extracting an identifier, from the request, identifying a notification service.

6. The system of claim 1, the method comprising:

extracting an identifier, from the request, identifying a queue associated with the client.

7. The system of claim 1, the method comprising:

associating a time to live with the client, such that if the client times out after a predetermined time, the subscription is removed from the soft memory.

8. A method, comprising:

requesting a subscription corresponding to a change to data;

receiving a notification of the change from a server;

responsive to receiving the notification, sending a synchronization request, associated with the change, to the server; and

participating in synchronization with the server, the synchronization corresponding to at least the change.

9. The method of claim 8, at least some of at least one of the requesting, the receiving, the sending, or the participating performed at least in part by a client.

10. The method of claim 8, the receiving a notification comprising receiving an indication of the change from a notification service, the indication originating from a subscription service.

11. The method of claim 8, comprising storing information associated with the subscription.

12. The method of claim 8, comprising:

including an identifier, in the synchronization request, identifying a notification service.

13. The method of claim 8, comprising:

including an identifier, in the synchronization request, identifying a queue associated with a client.

14. The method of claim 8, comprising:

sending a request to a notification service to create a queue.

15. A computer readable medium comprising instructions that when executed, perform a method comprising:

detecting a change to data, the data comprised in a server;

storing, in a queue comprising information associated with one or more changes, an indication of at least one of the change or a subscription, by a client, corresponding to the change;

providing a notification of the change to the client;

receiving a request, associated with the change, from the client; and

responsive to the request, providing for synchronization between the server and the client, the synchronization corresponding to at least the change.

16. The computer readable medium of claim 15, the queue comprised in soft memory.

17. The computer readable medium of claim 15, the providing a notification comprising:

providing, from a subscription service, an indication of the change to a notification service.

18. The computer readable medium of claim 17, the notification service configured to create one or more queues and the subscription service configured to instruct the notification service into which queue of the one or more queues to store the indication of the change.

19. The computer readable medium of claim 15, the method comprising:

extracting an identifier, from the request, identifying a notification service.

20. The computer readable medium of claim 15, the method comprising:

extracting an identifier, from the request, identifying a queue associated with the client.