Distributed and optimized garbage collection of remote and exported table handle links to update propagation graph nodes

1. A system for managing distributed client-server object handles, the system comprising:

a remote client computer containing a first one or more hardware processors;

a server computer containing a second one or more hardware processors;

the remote client computer containing a first computer readable data storage device coupled to the first one or more hardware processors, the first computer readable data storage device having stored thereon software instructions that, when executed by the first one or more hardware processors, cause the first one or more hardware processors to perform first operations including:

creating a remote object handle manager;

establishing a connection with a remote query processor on the server computer;

establishing a liveness indication system with the remote query processor;

receiving, from the remote query processor, exported object handle information to construct a remote object handle, including an exported object identifier, the exported object identifier identifying an exported object;

the remote object handle manager constructing the remote object handle;

the remote object handle manager monitoring liveness of all client objects that depend on the remote object handle, the remote object handle depending on the exported object and indirectly depending on the exported object's dependencies;

the remote object handle manager sending a release notification to the remote query processor including the exported object identifier, after no client objects depend on the exported object;

the server computer containing a second computer readable data storage device coupled to the second one or more hardware processors, the second computer readable data storage device having stored thereon software instructions that, when executed by the second one or more hardware processors, cause the second one or more hardware processors to perform second operations including:

creating a remote query processor, the remote query processor performing remote query processor operations including:

creating an exported object handle manager;

sending the exported object handle information including the exported object identifier from the exported object handle manager to the remote client computer; and

preserving a liveness of the exported object at least until any of the following events:

receipt of the release notification from the remote table handle manager; and

the liveness indication system determines the remote client computer is not connected,

wherein the remote query processor operations further comprise:

the remote query processor receiving a transmitted user query task from the remote client computer;

executing the transmitted user query task; and

upon executing an instruction from the user query task to export an object, creating an exported object handle.

2. A system for managing distributed client-server object handles, the system comprising:

a remote client computer containing a first one or more hardware processors;

a server computer containing a second one or more hardware processors;

the remote client computer containing a first computer readable data storage device coupled to the first one or more hardware processors, the first computer readable data storage device having stored thereon software instructions that, when executed by the first one or more hardware processors, cause the first one or more hardware processors to perform first operations including:

creating a remote object handle manager;

establishing a connection with a remote query processor on the server computer;

establishing a liveness indication system with the remote query processor;

receiving, from the remote query processor, exported object handle information to construct a remote object handle, including an exported object identifier, the exported object identifier identifying an exported object;

the remote object handle manager constructing the remote object handle;

the remote object handle manager monitoring liveness of all client objects that depend on the remote object handle, the remote object handle depending on the exported object and indirectly depending on the exported object's dependencies;

the remote object handle manager sending a release notification to the remote query processor including the exported object identifier, after no client objects depend on the exported object;

the server computer containing a second computer readable data storage device coupled to the second one or more hardware processors, the second computer readable data storage device having stored thereon software instructions that, when executed by the second one or more hardware processors, cause the second one or more hardware processors to perform second operations including:

creating a remote query processor, the remote query processor performing remote query processor operations including:

creating an exported object handle manager;

sending the exported object handle information including the exported object identifier from the exported object handle manager to the remote client computer; and

preserving a liveness of the exported object at least until any of the following events:

receipt of the release notification from the remote table handle manager; and

the liveness indication system determines the remote client computer is not connected,

wherein the remote object handle manager monitoring of client object liveness comprises:

maintaining a remote object handle reference count on the remote object handle;

decrementing the remote object handle reference count after a dependent client object no longer depends on the remote object handle; and

when the remote object handle reference count after decrementing is zero, sending a digital message to the remote query processor to release an associated exported object handle.

3. A method for managing distributed client-server object handles, the method comprising:

creating a remote object handle manager;

establishing a connection with a remote query processor on a server computer;

establishing a liveness indication system with the remote query processor;

receiving, from the remote query processor, exported object handle information to construct a remote object handle, including an exported object identifier, the exported object identifier identifying an exported object;

the remote object handle manager constructing the remote object handle;

the remote object handle manager monitoring liveness of all client objects that depend on the remote object handle, the remote object handle depending on the exported object and indirectly depending on the exported object's dependencies;

the remote object handle manager sending a release notification to the remote query processor including the exported object identifier, after no client objects depend on the exported object;

creating the remote query processor, the remote query processor performing operations including:

creating an exported object handle manager;

sending the exported object handle information including the exported object identifier from the exported object handle manager to a remote client computer; and

preserving a liveness of the exported object at least until receipt of the release notification from the remote object handle manager or until the liveness indication system determines the remote client computer is not connected,

wherein the remote query processor operations further comprise:

the remote query processor receiving a transmitted user query task from a remote client computer;

executing the transmitted user query task; and

upon executing an instruction from the user query task to export an object, creating an exported object handle.

4. A method for managing distributed client-server object handles, the method comprising:

creating a remote object handle manager;

establishing a connection with a remote query processor on a server computer;

establishing a liveness indication system with the remote query processor;

receiving, from the remote query processor, exported object handle information to construct a remote object handle, including an exported object identifier, the exported object identifier identifying an exported object;

the remote object handle manager constructing the remote object handle;

the remote object handle manager monitoring liveness of all client objects that depend on the remote object handle, the remote object handle depending on the exported object and indirectly depending on the exported object's dependencies;

the remote object handle manager sending a release notification to the remote query processor including the exported object identifier, after no client objects depend on the exported object;

creating the remote query processor, the remote query processor performing operations including:

creating an exported object handle manager;

sending the exported object handle information including the exported object identifier from the exported object handle manager to a remote client computer; and

preserving a liveness of the exported object at least until receipt of the release notification from the remote object handle manager or until the liveness indication system determines the remote client computer is not connected;

the remote object handle manager monitoring a handle cleanup reference queue;

after a handle cleanup reference appears in the handle cleanup reference queue, invoking a handle cleanup reference cleanup method;

the handle cleanup reference cleanup method decrementing a remote object handle reference count on a remote object handle associated with the handle cleanup reference;

the handle cleanup reference cleanup method removing the handle cleanup reference from a set of handle cleanup references monitored by the remote object handle manager;

when the remote object handle reference count after decrementing is zero, sending a digital message to the remote query processor to release an associated exported object handle; and

when the remote object handle reference count after decrementing is greater than zero, maintaining a strong reference to the remote object handle in order to ensure liveness for dependent client objects.

5. A nontransitory computer readable medium having stored thereon software instructions that, when executed by one or more processors, cause the one or more processors to perform operations including:

creating a remote object handle manager;

establishing a connection with a remote query processor on a server computer;

establishing a liveness indication system with the remote query processor;

receiving from the remote query processor, exported object handle information to construct a remote object handle, including an exported object identifier, the exported object identifier identifying an exported object;

the remote object handle manager constructing a remote object handle;

the remote object handle manager monitoring liveness of all client objects that depend on the remote object handle, the remote object handle depending on the exported object and indirectly depending on the exported object's dependencies;

the remote object handle manager sending a release notification to the remote query processor including the exported object identifier, after no client objects depend on the exported object;

the server computer containing a computer readable data storage device coupled to one or more hardware processors, the computer readable data storage device having stored thereon software instructions that, when executed by the one or more hardware processors, cause the one or more hardware processors to perform operations including:

creating a remote query processor, the remote query processor performing operations including:

creating an exported object handle manager;

sending the exported object handle information including the exported object identifier from the exported object handle manager to the remote client;

preserving a liveness of the exported object until receipt of the release notification from the remote object handle manager or until the liveness indication system determines the remote client is not connected;

the remote query processor receiving a transmitted user query task from the remote client computer;

executing the transmitted user query task; and

upon executing an instruction from the user query task to export an object, creating an exported object handle.

6. A nontransitory computer readable medium having stored thereon software instructions that, when executed by one or more processors, cause the one or more processors to perform operations including:

creating a remote object handle manager;

establishing a connection with a remote query processor on a server computer;

establishing a liveness indication system with the remote query processor;

receiving from the remote query processor, exported object handle information to construct a remote object handle, including an exported object identifier, the exported object identifier identifying an exported object;

the remote object handle manager constructing a remote object handle;

the remote object handle manager monitoring liveness of all client objects that depend on the remote object handle, the remote object handle depending on the exported object and indirectly depending on the exported object's dependencies;

the remote object handle manager sending a release notification to the remote query processor including the exported object identifier, after no client objects depend on the exported object;

the server computer containing a computer readable data storage device coupled to one or more hardware processors, the computer readable data storage device having stored thereon software instructions that, when executed by the one or more hardware processors, cause the one or more hardware processors to perform operations including:

creating a remote query processor, the remote query processor performing operations including:

creating an exported object handle manager;

sending the exported object handle information including the exported object identifier from the exported object handle manager to the remote client; and

preserving a liveness of the exported object until receipt of the release notification from the remote object handle manager or until the liveness indication system determines the remote client is not connected;

the remote object handle manager monitoring a handle cleanup reference queue;

after a handle cleanup reference appears in the handle cleanup reference queue, invoking a handle cleanup reference cleanup method;

the handle cleanup reference cleanup method decrementing a remote object handle reference count on a remote object handle associated with the handle cleanup reference;

the handle cleanup reference cleanup method removing the handle cleanup reference from a set of handle cleanup references monitored by the remote object handle manager;

when the remote object handle reference count after decrementing is zero, sending a digital message to the remote query processor to release an associated exported object handle; and

when the remote object handle reference count after decrementing is greater than zero, maintaining a strong reference to the remote object handle in order to ensure liveness for dependent client objects.

7. A system for managing distributed client-server object handles, the system comprising:

a remote client computer containing a first one or more hardware processors;

a server computer containing a second one or more hardware processors;

the remote client computer containing a first computer readable data storage device coupled to the first one or more hardware processors, the first computer readable data storage device having stored thereon software instructions that, when executed by the first one or more hardware processors, cause the first one or more hardware processors to perform first operations including:

creating a remote object handle manager;

establishing a connection with a remote query processor on the server computer;

establishing a liveness indication system with the remote query processor;

receiving, from the remote query processor, exported object handle information to construct a remote object handle, including an exported object identifier, the exported object identifier identifying an exported object;

the remote object handle manager constructing the remote object handle;

the remote object handle manager monitoring liveness of all client objects that depend on the remote object handle, the remote object handle depending on the exported object and indirectly depending on the exported object's dependencies;

the remote object handle manager sending a release notification to the remote query processor including the exported object identifier, after no client objects depend on the exported object;

the server computer containing a second computer readable data storage device coupled to the second one or more hardware processors, the second computer readable data storage device having stored thereon software instructions that, when executed by the second one or more hardware processors, cause the second one or more hardware processors to perform second operations including:

creating a remote query processor, the remote query processor performing remote query processor operations including:

creating an exported object handle manager;

sending the exported object handle information including the exported object identifier from the exported object handle manager to the remote client computer; and

preserving a liveness of the exported object at least until any of the following events:

receipt of the release notification from the remote table handle manager; and

the liveness indication system determines the remote client computer is not connected,

wherein the remote object handle manager monitoring of client object liveness comprises:

the remote object handle manager monitoring a handle cleanup reference queue;

after a handle cleanup reference appears in the handle cleanup reference queue, invoking a handle cleanup reference cleanup method;

the handle cleanup reference cleanup method removing the handle cleanup reference from a set of handle cleanup references monitored by the remote object handle manager, thereby eliminating all strong references to the handle cleanup reference; and

the handle cleanup reference cleanup method sending a digital message to the remote query processor to release an associated exported object handle.

8. A system for managing distributed client-server object handles, the system comprising:

a remote client computer containing a first one or more hardware processors;

a server computer containing a second one or more hardware processors;

the remote client computer containing a first computer readable data storage device coupled to the first one or more hardware processors, the first computer readable data storage device having stored thereon software instructions that, when executed by the first one or more hardware processors, cause the first one or more hardware processors to perform first operations including:

creating a remote object handle manager;

establishing a connection with a remote query processor on the server computer;

establishing a liveness indication system with the remote query processor;

receiving, from the remote query processor, exported object handle information to construct a remote object handle, including an exported object identifier, the exported object identifier identifying an exported object;

the remote object handle manager constructing the remote object handle;

the remote object handle manager monitoring liveness of all client objects that depend on the remote object handle, the remote object handle depending on the exported object and indirectly depending on the exported object's dependencies;

the remote object handle manager sending a release notification to the remote query processor including the exported object identifier, after no client objects depend on the exported object;

the server computer containing a second computer readable data storage device coupled to the second one or more hardware processors, the second computer readable data storage device having stored thereon software instructions that, when executed by the second one or more hardware processors, cause the second one or more hardware processors to perform second operations including:

creating a remote query processor, the remote query processor performing remote query processor operations including:

creating an exported object handle manager;

sending the exported object handle information including the exported object identifier from the exported object handle manager to the remote client computer; and

preserving a liveness of the exported object at least until any of the following events:

receipt of the release notification from the remote table handle manager; and

the liveness indication system determines the remote client computer is not connected,

wherein the remote object handle manager monitoring of client object liveness comprises:

the remote object handle manager monitoring a handle cleanup reference queue;

after a handle cleanup reference appears in the handle cleanup reference queue, invoking a handle cleanup reference cleanup method;

the handle cleanup reference cleanup method decrementing a remote object handle reference count on a remote object handle associated with the handle cleanup reference;

the handle cleanup reference cleanup method removing the handle cleanup reference from a set of handle cleanup references monitored by the remote object handle manager; and

when the remote object handle reference count after decrementing is zero, sending a digital message to the remote query processor to release an associated exported object handle.

9. A system for managing distributed client-server object handles, the system comprising:

a remote client computer containing a first one or more hardware processors;

a server computer containing a second one or more hardware processors;

the remote client computer containing a first computer readable data storage device coupled to the first one or more hardware processors, the first computer readable data storage device having stored thereon software instructions that, when executed by the first one or more hardware processors, cause the first one or more hardware processors to perform first operations including:

creating a remote object handle manager;

establishing a connection with a remote query processor on the server computer;

establishing a liveness indication system with the remote query processor;

receiving, from the remote query processor, exported object handle information to construct a remote object handle, including an exported object identifier, the exported object identifier identifying an exported object;

the remote object handle manager constructing the remote object handle;

the remote object handle manager monitoring liveness of all client objects that depend on the remote object handle, the remote object handle depending on the exported object and indirectly depending on the exported object's dependencies;

the remote object handle manager sending a release notification to the remote query processor including the exported object identifier, after no client objects depend on the exported object;

the server computer containing a second computer readable data storage device coupled to the second one or more hardware processors, the second computer readable data storage device having stored thereon software instructions that, when executed by the second one or more hardware processors, cause the second one or more hardware processors to perform second operations including:

creating a remote query processor, the remote query processor performing remote query processor operations including:

creating an exported object handle manager;

sending the exported object handle information including the exported object identifier from the exported object handle manager to the remote client computer; and

preserving a liveness of the exported object at least until any of the following events:

receipt of the release notification from the remote table handle manager; and

the liveness indication system determines the remote client computer is not connected,

wherein the remote query processor preserving a liveness of the exported object comprises:

maintaining a reference count associated with the exported object;

decrementing the reference count associated with the exported object after receipt of a release notification from the remote table handle manager;

decrementing the reference count associated with the exported object after the liveness indication system determines the remote client computer is not connected;

when the remote object handle reference count after decrementing is zero, removing a strong reference to the exported object from the exported object handle; and

when the remote object handle reference count after decrementing is greater than zero, maintaining a strong reference to the exported object from the exported object handle.

10. A method for managing distributed client-server object handles, the method comprising:

creating a remote object handle manager;

establishing a connection with a remote query processor on a server computer;

establishing a liveness indication system with the remote query processor;

receiving, from the remote query processor, exported object handle information to construct a remote object handle, including an exported object identifier, the exported object identifier identifying an exported object;

the remote object handle manager constructing the remote object handle;

the remote object handle manager monitoring liveness of all client objects that depend on the remote object handle, the remote object handle depending on the exported object and indirectly depending on the exported object's dependencies;

the remote object handle manager sending a release notification to the remote query processor including the exported object identifier, after no client objects depend on the exported object;

creating the remote query processor, the remote query processor performing operations including:

creating an exported object handle manager;

sending the exported object handle information including the exported object identifier from the exported object handle manager to a remote client computer; and

preserving a liveness of the exported object at least until receipt of the release notification from the remote object handle manager or until the liveness indication system determines the remote client computer is not connected,

wherein the preserving a liveness of the exported object comprises:

maintaining a reference count associated with the exported object;

decrementing the reference count associated with the exported object after receipt of a release notification from the remote table handle manager;

decrementing the reference count associated with the exported object after the liveness indication system determines the remote client computer is not connected;

when the remote object handle reference count after decrementing is zero, removing a strong reference to the exported object from the exported object handle; and

when the remote object handle reference count after decrementing is greater than zero, maintaining a strong reference to the exported object from the exported object handle.