System and method for propagating scene information to renderers in a multi-user, multi-scene environment
A system and method for propagating scene information to a renderer. In one embodiment, the system includes: (1) an update request receiver operable to receive an update request from the renderer and determine a point from which the renderer is to be updated and (2) an update propagator associated with the update request receiver and operable to employ a graph containing scene information to construct a change list corresponding to the update request and transmit the change list toward the renderer.
1. A system for propagating scene information to a renderer, comprising:
an update request receiver operable to receive update requests from said renderer and determine a point from which said renderer is to be updated, wherein said update requests include requests for changes made to said scene information while said renderer was inactive; and
an update propagator associated with said update request receiver and operable to employ a graph containing scene information to construct a change list in response to said update request and transmit said change list toward said renderer, said system and renderer implemented on a cloud server.
2. The system as recited in claim 1 wherein said renderer is associated with at least one virtual machine corresponding to a user.
3. The system as recited in claim 1 wherein said graph is a directed acyclic graph containing nodes selected from the group consisting of:
transformations,
object groups, and
object instances.
4. The system as recited in claim 1 wherein said change list identifies objects and corresponding object changes.
5. The system as recited in claim 1 wherein said renderer is registered in a database associated with said update request receiver, said database including said point.
6. The system as recited in claim 1 wherein said update propagator is further configured to generate a tree by unfolding said graph and construct said change list from said tree.
7. The system as recited in claim 1 wherein said renderer is configured to generate a video stream using said change list, said video stream transmitted from said cloud server to a client platform.
8. A method of propagating scene information to a renderer in a multi-user, multi-scene environment, comprising:
receiving an update request from a renderer associated with a virtual machine, wherein said update request includes a request for changes made to said scene information while said renderer was inactive;
determining a point from which said renderer is to be updated;
constructing a change list in response to said update request employing a graph containing scene information; and
transmitting said change list to allow said renderer to update a local version of said graph, wherein said receiving, determining, constructing, and transmitting are performed on a cloud server.
9. The method as recited in claim 8 wherein said renderer is associated with at least one virtual machine corresponding to a user.
10. The method as recited in claim 8 wherein said graph is a directed acyclic graph containing nodes selected from the group consisting of:
transformations,
object groups, and
object instances.
11. The method as recited in claim 8 wherein said change lists identify objects and corresponding object changes.
12. The method as recited in claim 8 wherein said renderer is registered in a database, said database including said point.
13. The method as recited in claim 8 further comprising generating trees by unfolding said graph and constructing said change lists from said trees.
14. The method as recited in claim 8 wherein said renderer is configured to generate video streams using said change lists, said video stream transmitted from said cloud server to a client platform.
15. A multi-user, multi-scene system, comprising:
a database operable to store a master Directed Acyclic Graph (DAG) containing scene information;
a plurality of renderers operable to render video streams using respective local versions of said master DAG;
an update request receiver associated with said database and operable to receive update requests from said renderers and determine points from which said respective local versions of said master DAG are to be updated, wherein said update requests include requests for changes made to said master DAG while said renderer was inactive; and
an update propagator associated with said update request receiver and operable to employ said master DAG to construct change lists in response to said update requests and transmit said change lists to said renderers, said multi-user, multi-scene system implemented on a cloud server.
16. The system as recited in claim 15 wherein each of said renderers is associated with at least one virtual machine corresponding to a user.
17. The system as recited in claim 15 wherein said master DAG contains nodes selected from the group consisting of:
transformations,
object groups, and
object instances.
18. The system as recited in claim 15 wherein said change lists identify objects and corresponding object changes.
19. The system as recited in claim 15 wherein said database includes said points.
20. The system as recited in claim 15 wherein said update propagator is further configured to generate trees by unfolding said graph and construct said change lists from said trees.