Storing state in a dynamic content routing network
A client module of an object state storage is configured to identify a live object at a client. The client module is further configured to receive an update message for the live object from storage, the update message is stored by an object ID associated with the live object, and the update message allowing the property to be updated for the live object at the client in real-time. The client module is further configured to transmit the update message for the live object to the client.
1. A method to update a property of a live object at a client, the method comprising:
identifying the live object at the client;
receiving object data associated with the live object;
extracting an object ID from the object data, wherein the object ID identifies a point in a document object model;
receiving an update message for the live object from an object state storage, the update message comprising data that, upon processing, causes a change to the a property of the live object being displayed at the client in real-time, wherein the object state storage is in communication with a dynamic content routing network, and is configured to store the update message at least in part using the object ID and to verify that the update message is from a valid source; and processing, in response to verification that the update message is from a valid source, the update message.
2. The method of claim 1 , wherein the object state storage is in communication with the dynamic content routing network via the Internet.
3. The method of claim 1 , further comprising, transmitting the update message to the client.
4. The method of claim 1 , further comprising, authenticating the client.
5. The method of claim 4 , wherein the authenticating the client comprises receiving client's credentials from the client.
6. The method of claim 4 , wherein the authenticating the client comprises receiving a token from the client, wherein the token represents the client's successful authentication with a node within the dynamic content routing network.
7. The method of claim 1 , wherein the update message is stored in a data structure configured to provide fast access.
8. The method of claim 1 , further comprising, receiving a second update message, the second update message comprising data that, upon processing, causes another change to the property of the live object.
9. The method of claim 1 , wherein the object ID further comprises a provider ID.
10. A hardware-based dynamic content routing network, comprising:
at least one processor configured to:
identify a live object at a client;
receive object data associated with the live object;
extract an object ID from the object data, wherein the object ID identifies a point in a document object model;
receive an update message for the live object from an object state storage, the update message comprising data that, upon processing, causes a change to a property of the live object being displayed at the client in real-time, wherein the object state storage is in communication with the a dynamic content routing network and is configured to store the update message at least in part using the object ID and to verify that the update message is from a valid source; and process, in response to verification that the update message is from a valid source, the update message.
11. The hardware-based dynamic content routing network of claim 10 , wherein the object state storage is in communication with the dynamic content routing network via the Internet.
12. The hardware-based dynamic content routing network of claim 10 , wherein the at least one processor is further configured to:
retrieve the update message from a storage device based on the object ID.
13. The hardware-based dynamic content routing network of claim 10 , wherein the update message is stored in a data structure configured to provide fast access.
14. The hardware-based dynamic content routing network of claim 10 , wherein the at least one processor is further configured to determine whether to store the update message.
15. The hardware-based dynamic content routing network of claim 10 , wherein the object ID further comprises a provider ID.
16. The hardware-based dynamic content routing network of claim 10 , wherein the at least one processor is further configured to authenticate the client.
17. The hardware-based dynamic content routing network of claim 10 , wherein the at least one processor is further configured to authenticate the client by receiving client's credentials from the client.
18. The hardware-based dynamic content routing network of claim 17 , wherein the at least one processor is further configured to receive tokens from the client, wherein the tokens represent the client's successful authentication with a node.