Efficient communication in a client-server scene graph system
First Claim
1. A method comprising:
- a client applying a plurality of changes to a client branch graph, wherein the client branch graph is maintained in a memory space which has been allocated to the client;
the client recording the plurality of changes to the client branch graph in a change store also maintained in the memory space;
the client transferring a first set of one or more protocol requests including one or more batch protocol requests to a display server, wherein the first set of protocol requests contain data from the change store specifying the plurality of changes, wherein the display server is configured to apply the plurality of changes to a remote branch graph;
wherein each of said batch protocol requests include two or more changes of said plurality of changes.
2 Assignments
0 Petitions
Accused Products
Abstract
A system and method for communicating 3D branch graph data and updates to branch graph data between clients and a display server in a 3D window system. A client locally creates a branch graph. When the client ready to make the branch graph live remote, it sends the branch graph to the display server using at least one batch protocol request. The display server builds a copy of the branch graph and attaches it to a centralized scene graph that it manages. The client may subsequently induce detachment of the branch graph from the scene graph. The client may buffer up changes to the local branch graph when its remote counterpart (in the display server) is not attached to the scene graph. The buffered changes may be sent to the display server using at least one batch protocol request when the client is again ready to make the branch graph live remote.
-
Citations
32 Claims
-
1. A method comprising:
-
a client applying a plurality of changes to a client branch graph, wherein the client branch graph is maintained in a memory space which has been allocated to the client;
the client recording the plurality of changes to the client branch graph in a change store also maintained in the memory space;
the client transferring a first set of one or more protocol requests including one or more batch protocol requests to a display server, wherein the first set of protocol requests contain data from the change store specifying the plurality of changes, wherein the display server is configured to apply the plurality of changes to a remote branch graph;
wherein each of said batch protocol requests include two or more changes of said plurality of changes. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 29, 30)
-
-
9. The method of 1, wherein the one or more protocol requests have a packet structure defined by the X11 client-server protocol.
-
25. A method comprising:
-
a display server receiving a first set of one or more protocol requests including one or more batch protocol requests from a client, wherein the first set of one or more protocol requests includes data specifying a plurality of changes which have been applied to a client branch graph, wherein each of said batch protocol requests includes two or more of the plurality of changes;
the display server applying the plurality of changes to a remote branch graph;
the display server attaching the remote branch graph to a scene graph and rendering the scene graph. - View Dependent Claims (26, 27, 28, 31, 32)
-
Specification