Managing objects using a client-server bridge

Abstract

A method for supporting communication between a client and a server includes receiving a first message from a client. The method also includes creating an object in response to the first message. The method also includes sending a response to the first message to the client. The method also includes receiving changes to the object from a server. The method also includes storing the changes to the object. The method also includes receiving a second message from the client. The method also includes sending the stored changes to the client with a response to the second message.

What is claimed is: 
     
         1 . A method for supporting communication between a client and a server, including
 receiving a first message from a client;   creating an object in response to the first message;   sending a response to the first message to the client;   receiving changes to the object from a server;   storing the changes to the object;   receiving a second message from the client; and   sending the stored changes to the client with a response to the second message.   
     
     
         2 . The method of  claim 1 , wherein storing the changes includes creating a log of changes and wherein sending the stored changes to the client includes sending the log of changes. 
     
     
         3 . The method of  claim 1 , wherein storing the changes includes updating a current state of the object and wherein sending the stored changes to the client includes sending the current state of the object. 
     
     
         4 . The method of  claim 1 , wherein receiving the first message from the client includes receiving a temporary identifier for a client object; creating the object includes obtaining a permanent identifier for the object; and sending the response to the first message includes sending a mapping between the temporary identifier and the permanent identifier. 
     
     
         5 . The method of  claim 4 , wherein obtaining a permanent identifier includes sending a server message to the server. 
     
     
         6 . The method of  claim 5 , wherein sending the server message includes interleaving the server message with other server messages. 
     
     
         7 . The method of  claim 1 , further including registering interest in the object with the server. 
     
     
         8 . The method of  claim 7 , wherein receiving changes to the object includes receiving changes to the object associated with events generated by the server. 
     
     
         9 . The method of  claim 1 , wherein receiving the first message includes utilizing a first protocol, and receiving the changes to the object includes utilizing a second protocol different from the first protocol. 
     
     
         10 . The method of  claim 1 , further including storing changes for multiple objects for multiple clients. 
     
     
         11 . The method of  claim 1 , wherein the object corresponds to a portion of a dataflow graph that includes multiple nodes representing components of the dataflow graph and links between the nodes representing flows of data between the components. 
     
     
         12 . The method of  claim 11 , wherein receiving the first message from the client includes receiving a value of a parameter for defining at least one characteristic of a component of the dataflow graph. 
     
     
         13 . The method of  claim 11 , further including providing an interface that receives one or more parameters for defining respective characteristics of components of the dataflow graph. 
     
     
         14 . The method of  claim 13 , wherein the interface displays multiple user interface elements with relationships among the user interface elements being based on dependencies between components of the dataflow graph. 
     
     
         15 . The method of  claim 14 , wherein the relationships are defined by a specification stored on the server. 
     
     
         16 . The method of  claim 11 , wherein receiving the first message includes receiving a request for intermediate data; and
 creating the object includes:
 compiling the portion of the dataflow graph, and 
 producing output to an output dataset by executing the compiled portion of the dataflow graph. 
   
     
     
         17 . The method of  claim 16 , wherein creating the object further includes:
 determining a first set of components required to generate the intermediate data;   disabling components in the dataflow graph that are not in the first set of components; and   creating an intermediate data sink coupled to the dataflow graph to store the output dataset.   
     
     
         18 . The method of  claim 17 , wherein determining the first set of components includes identifying links that do not connect a data source to the intermediate data sink. 
     
     
         19 . The method of  claim 17 , wherein creating an intermediate data sink includes determining that a link to the intermediate data sink represents a parallel data flow; and
 creating a parallel data sink as the intermediate data sink.   
     
     
         20 . A computer-readable medium storing a computer program for supporting communication between a client and a server, the computer program including instructions for causing a computer to:
 receive a first message from a client;   create an object in response to the first message;   send a response to the first message to the client;   receive changes to the object from a server;   store the changes to the object;   receive a second message from the client; and   send the stored changes to the client with a response to the second message.   
     
     
         21 . A system for supporting communication between a client and a server, the system including:
 a server including at least one processor; and   a bridge including at least one processor configured to manage objects in the system, where the managing includes
 receiving a first message from a client, 
 creating an object in response to the first message, 
 sending a response to the first message to the client, 
 receiving changes to the object from the server, 
 storing the changes to the object, 
 receiving a second message from the client, and 
 sending the stored changes to the client with a response to the second message. 
   
     
     
         22 . A system for supporting communication between a client and a server, the system including:
 means for serving data; and   means for managing objects in the system, wherein the managing includes
 receiving a first message from a client, 
 creating an object in response to the first message, 
 sending a response to the first message to the client, 
 receiving changes to the object from the means for serving data, 
 storing the changes to the object, 
 receiving a second message from the client, and 
 sending the stored changes to the client with a response to the second message.