SYSTEM AND METHOD FOR PROVIDING AN ACTIVELY INVALIDATED CLIENT-SIDE NETWORK RESOURCE CACHE

• US 20140280522A1
• Filed: 06/01/2014
• Published: 09/18/2014
• Est. Priority Date: 02/02/2011
• Status: Active Grant

• Current Assignee: IMVU Incorporated (IMVU)
• Original Assignee: IMVU Incorporated (IMVU)
• Inventors: Watte, Jon
• Granted Patent: US 9,578,081 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/18 Commands or executable codes
• CPC Class Codes: H04L 51/52 for supporting social networking services
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70

Abstract

A system and method for providing an actively invalidated client-side network resource cache are disclosed. A particular embodiment includes: a client configured to request, for a client application, data associated with an identifier from a server; the server configured to provide the data associated with the identifier, the data being subject to subsequent change, the server being further configured to establish a queue associated with the identifier at a scalable message queuing system, the scalable message queuing system including a plurality of gateway nodes configured to receive connections from client systems over a network, a plurality of queue nodes containing subscription information about queue subscribers, and a consistent hash table mapping a queue identifier requested on a gateway node to a corresponding queue node for the requested queue identifier; the client being further configured to subscribe to the queue at the scalable message queuing system to receive invalidation information associated with the data; the server being further configured to signal the queue of an invalidation event associated with the data; the scalable message queuing system being configured to convey information indicative of the invalidation event to the client; and the client being further configured to re-request the data associated with the identifier from the server upon receipt of the information indicative of the invalidation event from the scalable message queuing system.

Claims

1. A system for delivering data to a client application over a network, the system comprising:

a server in data communication with the network;

a client in data communication with the server via the network, a client application executing on the client;

a scalable message queuing system in data communication with the server and the client via the network, the scalable message queuing system including a plurality of gateway nodes configured to receive connections from client systems over a network, a plurality of queue nodes containing subscription information about queue subscribers, and a consistent hash table mapping a queue identifier requested on a gateway node to a corresponding queue node for the requested queue identifier;

the client being configured to request, for the client application, data associated with an identifier from the server;

the server being configured to provide the data associated with the identifier, the data being subject to subsequent change, the server being further configured to establish a queue associated with the identifier at the scalable message queuing system;

the client being further configured to subscribe to the queue at the scalable message queuing system to receive invalidation information associated with the data;

the server being further configured to signal the queue of an invalidation event associated with the data;

the scalable message queuing system being configured to convey information indicative of the invalidation event to the client; and

the client being further configured to re-request the data associated with the identifier from the server upon receipt of the information indicative of the invalidation event from the scalable message queuing system.

2. The system as claimed in claim 1 wherein the client request for data associated with the identifier is sent over a hypertext transfer protocol (HTTP) based protocol and the identifier for the data includes a uniform resource identifier (URI).

3. The system as claimed in claim 1 wherein the information indicative of the invalidation event is conveyed to the client via WebSocket protocol.

4. The system as claimed in claim 1 wherein the information indicative of the invalidation event includes the identifier of the data that was invalidated.

5. The system as claimed in claim 1 wherein the information indicative of the invalidation event includes a shortened version of the identifier of the data that was invalidated.

6. The system as claimed in claim 1 wherein the information indicative of the invalidation event is sent through the corresponding subscribed queue.

7. The system as claimed in claim 1 wherein the information indicative of the invalidation event is sent as a state update in a state mount that maps the identifier of the data to a version number.

8. The system as claimed in claim 1 wherein the server being further configured to provide the data associated with the identifier along with information identifying the established queue, the information identifying the established queue being transmitted together with the data as hypertext transfer protocol (HTTP) headers.

9. The system as claimed in claim 1 wherein the server being further configured to provide the data associated with the identifier along with information identifying the established queue and a mount, the information identifying the established queue and the mount being transmitted together with the data as hypertext transfer protocol (HTTP) headers.

10. The system as claimed in claim 1 wherein the server being further configured to provide the data associated with the identifier along with information identifying the established queue and a mount, the information identifying the established queue and the mount being transmitted together with the data as additional payload data.

11. The system as claimed in claim 1 wherein the server being further configured to provide the data associated with the identifier along with information identifying the established queue, the information identifying the established queue being transmitted as a payload response to another uniform resource identifier (URI).

12. A method comprising:

configuring, by use of a data processor, a client to request, for a client application, data associated with an identifier from a server;

configuring, by use of a data processor, the server to provide the data associated with the identifier, the data being subject to subsequent change, the server being further configured to establish a queue associated with the identifier at a scalable message queuing system, the scalable message queuing system including a plurality of gateway nodes configured to receive connections from client systems over a network, a plurality of queue nodes containing subscription information about queue subscribers, and a consistent hash table mapping a queue identifier requested on a gateway node to a corresponding queue node for the requested queue identifier;

configuring the client to subscribe to the queue at the scalable message queuing system to receive invalidation information associated with the data;

configuring the server to signal the queue of an invalidation event associated with the data;

configuring, by use of a data processor, the scalable message queuing system to convey information indicative of the invalidation event to the client; and

configuring the client to re-request the data associated with the identifier from the server upon receipt of the information indicative of the invalidation event from the scalable message queuing system.

13. The method as claimed in claim 12 wherein the client request for data associated with the identifier is sent over a hypertext transfer protocol (HTTP) based protocol and the identifier for the data includes a uniform resource identifier (URI).

14. The method as claimed in claim 12 wherein the information indicative of the invalidation event is conveyed to the client via WebSocket protocol.

15. The method as claimed in claim 12 wherein the information indicative of the invalidation event includes the identifier of the data that was invalidated.

16. The method as claimed in claim 12 wherein the information indicative of the invalidation event includes a shortened version of the identifier of the data that was invalidated.

17. The method as claimed in claim 12 wherein the information indicative of the invalidation event is sent through the corresponding subscribed queue.

18. The method as claimed in claim 12 wherein the information indicative of the invalidation event is sent as a state update in a state mount that maps the identifier of the data to a version number.

19. A non-transitory machine-useable storage medium embodying instructions which, when executed by a machine, cause the machine to:

configure a client to request, for a client application, data associated with an identifier from a server;

configure the server to provide the data associated with the identifier, the data being subject to subsequent change, the server being further configured to establish a queue associated with the identifier at a scalable message queuing system, the scalable message queuing system including a plurality of gateway nodes configured to receive connections from client systems over a network, a plurality of queue nodes containing subscription information about queue subscribers, and a consistent hash table mapping a queue identifier requested on a gateway node to a corresponding queue node for the requested queue identifier;

configure the client to subscribe to the queue at the scalable message queuing system to receive invalidation information associated with the data;

configure the server to signal the queue of an invalidation event associated with the data;

configure the scalable message queuing system to convey information indicative of the invalidation event to the client; and

configure the client to re-request the data associated with the identifier from the server upon receipt of the information indicative of the invalidation event from the scalable message queuing system.

20. The machine-useable storage medium as claimed in claim 19 wherein the client request for data associated with the identifier is sent over a hypertext transfer protocol (HTTP) based protocol and the identifier for the data includes a uniform resource identifier (URI).