Efficient communication in a client-server scene graph system

• US 7,800,614 B2
• Filed: 02/09/2005
• Issued: 09/21/2010
• Est. Priority Date: 02/17/2004
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Oracle America, Inc. (Oracle Corporation)
• Inventors: Johnson, Deron D., Rushforth, Kevin C., Kawahara, Hideya, Twilleager, Douglas C., Byrne, Paul V.
• Primary Examiner(s): Amini; Javid A
• Application Number:
  US11/054,154
• Publication Number:
  US 20050182844A1
• Time in Patent Office: 2,050 Days
• Field of Search: 345/440
• US Class Current: 345/440
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 2209/541 Client-server
• CPC Class Codes: G06F 9/452 Remote windowing, e.g. X-Window System, desktop virtualisation protocols for virtual reality H04L67/131
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: H04L 67/131 Protocols for games, networked simulations or virtual reality

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.

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, wherein the client branch graph includes one or more nodes organized in a hierarchical structure, wherein at least one of the one or more nodes include graphics data;

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 one of said one or more batch protocol requests includes two or more changes of said plurality of changes, wherein the two or more changes of said plurality of changes indicate changes to one or more graphical objects for a scene graph, wherein the one or more graphical objects are described by the client branch graph, and wherein multiple changes to the scene graph are included in each one of the one or more batch protocol requests.

2. The method of claim 1, wherein the display server is further configured to attach the remote branch graph to the scene graph and to render the scene graph.

3. The method of claim 2 further comprising:

the client transmitting a detachment request to the display server;

wherein the display server is further configured to detach the remote branch graph from the scene graph in response to receiving the detachment request.

4. The method of claim 3, wherein the display server is further configured to send the detached branch graph to the client.

5. The method of claim 1, wherein said recording of the plurality of changes is performed during a buffered mode of operation.

6. The method of claim 5, wherein the method further comprises:

the client determining that the buffered mode of operation has been disabled; and

the client transferring a separate protocol request to the display server for each change applied to the client branch graph after having determined that the buffered mode of operation has been disabled, wherein each separate protocol request specifies the corresponding change applied to the client branch graph.

7. The method of claim 1 further comprising:

the client creating the client branch graph in the memory space;

the client transferring a second set of protocol requests including one or more batch protocol requests to a display server, wherein the second set of protocol requests contains data specifying a copy of the client branch graph, wherein the display server is configured to receive the second set of protocol requests and construct the remote branch graph from the branch graph copy.

8. The method of claim 1, wherein the display server and client are processes executing on different computers.

10. The method of claim 1, wherein the display server is configured to attach the remote branch graph to the scene graph in response to receiving a corresponding command from the client, wherein the client branch graph is said to be live remote when the remote branch graph is attached to the scene graph, wherein the client is configured to perform said transferring of the first set of protocol requests containing said data in response to receiving a request to make to the client branch graph live remote.

11. The method of claim 10 further comprising:

the client transferring a separate protocol request to the display server for each change applied to the client branch graph after having determined that the remote branch graph has been attached to the client branch graph.

12. The method of claim 1, wherein said data specifying the plurality of changes includes a description of an addition of a node or subgraph to the client branch graph in the change store.

13. The method of claim 1, wherein said data specifying the plurality of changes includes, for each node of the client branch graph that has been modified by said changes to the client branch graph, (a) a list of the node attributes which have been modified and (b) values of the attributes indicated by the list.

14. The method of claim 1, wherein said data specifying the plurality of changes includes a list of identifiers identifying nodes and subgraphs that have been removed from the client branch graph.

15. The method of claim 1, wherein said data specifying the plurality of changes includes a list of nodes and subgraphs that have been added to the client branch graph.

16. The method of claim 5 further comprising:

the client determining that the buffered mode of operation has been disabled; and

in response to a determination that the buffered mode of operation has been disabled;

the client recording changes to a selected subset of nodes in the client branch graph in the change store;

the client sending the changes from the change store to the display server in a third set of protocol requests including one or more batch protocol requests;

the client separately sending each change that modifies any node in the client branch graph outside the selected subset to the display server.

17. The method of claim 16, wherein each node has an attribute that determines whether the node belongs to the selected subset, wherein the value of the attribute is modifiable by an application program.

18. The method of claim 1, wherein the client is configured to make the client branch graph live remote by sending a request to the display sever directing the display server to connect the remote branch graph to the scene graph;

wherein said plurality of changes to the client branch graph include changes to attributes of nodes of the client branch graph.

19. The method of claim 18 further comprising:

determining that a first node of the client branch graph has never been part of the client branch graph when the client branch graph was live remote;

transferring an entire state of the node to the display server in response to said determination that the first node has never been part of the client branch graph when the client branch graph was live remote.

20. The method of claim 1, wherein the client is configured to perform said recording and said transferring for a plurality of client branch graphs, wherein the client maintains a separate change store for each branch graph.

21. The method of claim 1, wherein the change store includes a union of node change stores, one per node of the client branch graph, wherein changes to attributes of each node are stored in the corresponding node change store.

22. The method of claim 1, wherein the client branch graph includes a plurality of nodes, wherein each node of the client branch graph includes a buffered changes attribute;

the method further comprising;

the client determining if the buffered changes for a first node is set to a first state in response to receiving a command to change an attribute of the first node;

the client transferring a singe protocol request corresponding to the command to the display server in the response to determining that the buffered changes attribute of the first node is set to the first state;

the client recording the change to the attribute in the change store in response to determining that the buffered changes attribute of the first node is set to a second state different from the first state.

23. The method of claim 22 further comprising:

transferring information representing changes that have accumulated for the first node from the change store to the display server in response to a determination that the buffered changes attribute of the first node has transitioned from the second state to the first state.

24. The method of claim 1 further comprising:

the client marking a node of the client branch graph as having been modified by one of said plurality of changes;

the client transferring an entire state of the node of the client branch graph to the display server in response to a synchronization condition for the node becoming true.

25. A computer-readable memory medium storing program instructions, wherein the program instructions are executable to implement the method recited in claim 1.

26. A system, comprising:

a processor; and

a memory storing program instructions, wherein the program instructions are executable by the processor to implement the method recited in claim 1.

9. The method of 1, wherein the one or more protocol requests have a packet structure defined by the X11 client-server protocol.

27. 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 at the client, wherein each one of said one or more batch protocol requests includes two or more of the plurality of changes, wherein the two or more of the plurality of changes indicate changes to one or more graphical objects for a scene graph, wherein the one or more graphical objects are described by the client branch graph, and wherein multiple changes to the scene graph are included in each one of the one or more batch protocol requests;

the display server applying the plurality of changes to a remote branch graph, wherein the remote branch graph includes one or more nodes organized in a hierarchical structure, wherein at least one of the one or more nodes include graphics data;

the display server attaching the remote branch graph to the scene graph and rendering the scene graph.

28. The method of claim 27 further comprising:

the display server receiving a second set of one or more protocol requests including one or more batch protocol requests from the client prior to receiving the first set of one or more protocol requests, wherein the second set of protocol requests contain a copy of the client branch graph;

the display server constructing the remote branch graph from the branch graph copy;

the display server attaching the branch graph copy to the scene graph.

29. The method of claims 27, wherein the display server is part of a 3D window system.

30. The method of claim 27, wherein the display server is configured to maintain a plurality of remote branch graphs corresponding to one or more clients.

31. A computer-readable memory medium storing program instructions, wherein the program instructions are executable to implement the method recited in claim 27.

32. A system, comprising:

a processor; and

a memory storing program instructions, wherein the program instructions are executable by the processor to implement the method recited in claim 27.