Storing state in a dynamic content routing network

• US 20050278726A1
• Filed: 08/05/2002
• Published: 12/15/2005
• Est. Priority Date: 12/18/2000
• Status: Active Grant

• Current Assignee: Intellectual Ventures I LLC (Intellectual Ventures LLC)
• Original Assignee: Shaw Parsing LLC (Intellectual Ventures LLC)
• Inventors: Cano, Charles E., Grimes, Jeff
• Granted Patent: US 7,127,720 B2
• Time in Patent Office: Days
• US Class Current: 719/315
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• 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/63 Routing a service request depending on the request content or context

Abstract

A dynamic content routing network routes update messages containing updates to properties of live objects from input sources to clients. The clients receive a web page having live objects, identify the object IDs associated with the objects, and contact an object state storage to obtain update messages specifying the objects'"'"'initial properties. The clients register the object IDs with the routing network. The routing network maintains a registry of object IDs and clients. The input source provides an update message to the routing network containing the object ID and data for updating a property of the object. The routing network routes update messages from the input source to the clients registered for the object ID contained in the message. Upon receipt of the message, a client updates the specified property of the live object. The update messages are also provided to, and stored by, the object state storage.

Claims

1. An object state storage for providing update messages to update properties of live objects at clients, the object state storage comprising:

a storage access module adapted to store and retrieve update messages for live objects;

an input handler module in communication with the storage access module and adapted to receive update messages for live objects and provide the update messages to the storage access module for storage; and

a client handler module in communication with the storage access module and adapted to receive identifications of live objects from the clients, obtain update messages for the identified live objects from the storage access module, and provide the update messages to the clients.

2. The object state storage of claim 1, wherein the storage access module is further adapted to interface with a memory store, wherein the memory store stores the update messages in a data structure adapted to provide fast access.

3. The object state storage of claim 1, wherein the update messages include object IDs identifying the live objects to which the update messages pertain and wherein the storage access module is adapted to store and access the update messages based on object ID.

4. The object state storage of claim 1, wherein the input handler module is adapted to receive the update messages from an input source, the input source also providing the update messages to a dynamic content routing network.

5. The object state storage of claim 1, wherein the input handler module is adapted to receive the update messages from a dynamic content routing network.

6. The object state storage of claim 1, wherein the input handler module is further adapted to receive and process control messages.

7. The object state storage of claim 1, wherein the input handler module is further adapted to determine whether to store a received update message.

8. The object state storage of claim 1, wherein the client handler module is adapted to receive object IDs identifying live objects from the clients.

9. A computer program product comprising:

a computer-readable medium having computer program code embodied therein for updating properties of live objects at a client, the computer program code adapted to;

identify the live objects at the client;

receive update messages for one or more of the live objects from an object state storage, each update message identifying a live object at the client and containing data for updating a property of the live object; and

process the update messages to cause the updates to the properties of the live objects.

10. The computer program product of claim 9, wherein identifying the live objects at the client comprises:

analyzing a web page displayed at the client to identify object IDs of live objects on the web page.

11. The computer program product of claim 9, wherein identifying the live objects at the client comprises:

receiving data responsive to a solicitation of input, the data identifying the live objects at the client.

12. The computer program product of claim 9, wherein the program code is further adapted to:

send a registration message indicating the live objects identified at the client to a remote routing network;

receive update messages from the remote routing network; and

process the update messages received from the remote routing network to cause the updates to the properties of the live objects.

13. The computer program product of claim 9, wherein processing the update message to cause the updates to the properties of the live objects comprises:

changing a property associated with a visual attribute of an identified live object.

14. The computer program product of claim 9, wherein processing the update message to cause the update to the properties of the live objects comprises:

changing a property associated with a non-visual attribute of an identified live object.

15. A system for updating properties of live objects at a plurality of clients, comprising:

a routing network in communication with the plurality of clients, the routing network adapted to maintain mappings between clients and live objects, to receive an update message from a remote input source including data for updating a property of an identified live object, and to route the update message to the clients according to the mappings; and

an object state storage adapted to connect with the clients, to receive and store the update message, and to provide the update message to the clients responsive to requests from the clients;

wherein each registered client is adapted to obtain an initial update message from the object state storage and subsequent update messages from the routing network and is further adapted to process the data to cause the update to the property of the live object.

16. The system of claim 15, wherein the object state storage is adapted to receive the update message from the remote input source.

17. The system of claim 15, wherein the object state storage is adapted to receive the update message from the routing network.

18. The system of claim 15, wherein each client executes an activation module adapted to enable identification of live objects at the client, obtain initial properties for the identified live objects from the object state storage, and register for subsequent updates to properties of the identified live objects with the routing network.

19. The system of claim 15, the routing network is further adapted to provide the activation module to the clients.

20. An object state storage for providing update messages to update properties of live objects at clients, the object state storage comprising:

means for storing and retrieving update messages for live objects;

means for receiving update messages for live objects and provide the update messages to the means for storing and retrieving; and

means for receiving identifications of live objects from the clients, obtaining update messages for the identified live objects from the means for storing and retrieving, and providing the update messages to the clients.

21. The object state storage of claim 20, wherein the means for storing and retrieving are further adapted to interface with a memory means for storing the update messages in a data structure adapted to provide fast access.

22. The object state storage of claim 20, wherein the update messages include object IDs identifying the live objects to which the update messages pertain and wherein the means for receiving update messages are adapted to store and access the update messages based on object ID.

23. The object state storage of claim 20, wherein the means for receiving update messages are adapted to receive the update messages from an input source, the input source also providing the update messages to a dynamic content routing network.

24. The object state storage of claim 20, wherein the means for receiving update messages are adapted to receive the update messages from a dynamic content routing network.

25. The object state storage of claim 20, wherein the means for receiving update messages are adapted to receive and process control messages.

26. The object state storage of claim 20, wherein the means for receiving update messages are adapted to determine whether to store a received update message.

27. The object state storage of claim 20, wherein the means for receiving identifications of live objects are adapted to receive object IDs identifying live objects from the clients.