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

• US 9,612,959 B2
• Filed: 05/14/2016
• Issued: 04/04/2017
• Est. Priority Date: 05/14/2015
• Status: Active Grant

• Current Assignee: Deephaven Data Labs, LLC
• Original Assignee: Walleye Software LLC
• Inventors: Kent, IV, David R., Caudy, Ryan, Wright, Charles, Teodorescu, Radu
• Primary Examiner(s): NGUYEN, PHONG H
• Application Number:
  US15/154,983
• Publication Number:
  US 20160335180A1
• Time in Patent Office: 325 Days
• Field of Search: 707814, 707769
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 12/0261 using reference counting
• CPC Class Codes: G06F 12/084 with a shared cache
• CPC Class Codes: G06F 12/1483 using an access-table, e.g. matrix or list
• CPC Class Codes: G06F 15/17331 Distributed shared memory [DSM], e.g. remote direct memory access [RDMA]
• CPC Class Codes: G06F 16/113 Details of archiving lifecycle management in storage systems G06F3/0649; backup systems G06F11/1446
• CPC Class Codes: G06F 16/144 Query formulation
• CPC Class Codes: G06F 16/162 Delete operations erasing in storage systems G06F3/0652
• CPC Class Codes: G06F 16/215 Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/221 Column-oriented storage; Management thereof
• CPC Class Codes: G06F 16/2228 Indexing structures
• CPC Class Codes: G06F 16/2237 Vectors, bitmaps or matrices
• CPC Class Codes: G06F 16/2246 Trees, e.g. B+trees
• CPC Class Codes: G06F 16/2255 Hash tables
• CPC Class Codes: G06F 16/2264 Multidimensional index structures
• CPC Class Codes: G06F 16/2272 Management thereof
• CPC Class Codes: G06F 16/2282 Tablespace storage structures; Management thereof
• CPC Class Codes: G06F 16/2291 : User-Defined Types; Storage management thereof
• CPC Class Codes: G06F 16/23 : Updating
• CPC Class Codes: G06F 16/2308 : Concurrency control transaction processing G06F9/466
• CPC Class Codes: G06F 16/2358 : Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/2365 : Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2372 : Updates performed during offline database operations
• CPC Class Codes: G06F 16/2379 : Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/242 : Query formulation
• CPC Class Codes: G06F 16/2428 : Query predicate definition using graphical user interfaces, including menus and forms G06F16/2423 takes precedence
• CPC Class Codes: G06F 16/245 : Query processing
• CPC Class Codes: G06F 16/2453 : Query optimisation
• CPC Class Codes: G06F 16/24534 : Query rewriting; Transformation
• CPC Class Codes: G06F 16/24535 : of sub-queries or views
• CPC Class Codes: G06F 16/24537 : of operators
• CPC Class Codes: G06F 16/24539 : using cached or materialised query results
• CPC Class Codes: G06F 16/2455 : Query execution
• CPC Class Codes: G06F 16/24553 : of query operations
• CPC Class Codes: G06F 16/2456 : Join operations
• CPC Class Codes: G06F 16/24561 : Intermediate data storage techniques for performance improvement
• CPC Class Codes: G06F 16/2457 : with adaptation to user needs
• CPC Class Codes: G06F 16/24575 : using context
• CPC Class Codes: G06F 16/248 : Presentation of query results
• CPC Class Codes: G06F 16/254 : Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses
• CPC Class Codes: G06F 16/27 : Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/278 : Data partitioning, e.g. horizontal or vertical partitioning
• CPC Class Codes: G06F 16/285 : Clustering or classification
• CPC Class Codes: G06F 16/9024 : Graphs; Linked lists G06F16/9027 takes precedence
• CPC Class Codes: G06F 16/907 : Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 16/951 : Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/9535 : Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 16/9538 : Presentation of query results
• CPC Class Codes: G06F 16/9566 : URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: G06F 16/9574 : of access to content, e.g. by caching
• CPC Class Codes: G06F 17/40 : Data acquisition and logging for input to computer G06F3/00
• CPC Class Codes: G06F 21/00 : Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
• CPC Class Codes: G06F 21/6209 : to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
• CPC Class Codes: G06F 2201/805 : Real-time
• CPC Class Codes: G06F 2201/84 : Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 2212/1052 : Security improvement
• CPC Class Codes: G06F 2212/154 : Networked environment
• CPC Class Codes: G06F 2212/163 : Server or database system
• CPC Class Codes: G06F 2212/60 : Details of cache memory
• CPC Class Codes: G06F 3/0481 : based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
• CPC Class Codes: G06F 3/0482 : Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G06F 3/0483 : Interaction with page-structured environments, e.g. book metaphor
• CPC Class Codes: G06F 3/04847 : Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
• CPC Class Codes: G06F 3/0485 : Scrolling or panning
• CPC Class Codes: G06F 3/04895 : Guidance during keyboard input operation, e.g. prompting
• CPC Class Codes: G06F 3/0605 : by facilitating the interaction with a user or administrator
• CPC Class Codes: G06F 3/0656 : Data buffering arrangements
• CPC Class Codes: G06F 3/067 : Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G06F 40/117 : Tagging; Marking up details of markup languages G06F40/143; Designating a block; Setting of attributes style sheets, e.g. eXtensible Stylesheet Language Transformation [XSLT], G06F40/154
• CPC Class Codes: G06F 40/134 : Hyperlinking
• CPC Class Codes: G06F 40/166 : Editing, e.g. inserting or deleting
• CPC Class Codes: G06F 40/174 : Form filling; Merging
• CPC Class Codes: G06F 40/177 : of tables; using ruled lines
• CPC Class Codes: G06F 40/18 : of spreadsheets form-filling G06F40/174
• CPC Class Codes: G06F 40/183 : Tabulation, i.e. one-dimensional positioning
• CPC Class Codes: G06F 40/216 : using statistical methods
• CPC Class Codes: G06F 40/274 : Converting codes to words; Guess-ahead of partial word inputs
• CPC Class Codes: G06F 8/30 : Creation or generation of source code
• CPC Class Codes: G06F 8/41 : Compilation
• CPC Class Codes: G06F 8/427 : Parsing
• CPC Class Codes: G06F 8/60 : Software deployment
• CPC Class Codes: G06Q 40/04 : Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
• CPC Class Codes: H04L 12/18 : for broadcast or conference , e.g. multicast
• CPC Class Codes: H04L 51/046 : Interoperability with other network applications or services
• CPC Class Codes: H04L 51/212 : using filtering or selective blocking
• CPC Class Codes: H04L 61/5069 : for group communication, multicast communication or broadcast communication
• CPC Class Codes: H04L 63/101 : Access control lists [ACL]
• CPC Class Codes: H04L 63/102 : Entity profiles
• CPC Class Codes: H04L 67/01 : Protocols
• CPC Class Codes: H04L 67/1001 : for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/141 : Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/34 : involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/56 : Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/566 : Grouping or aggregating service requests, e.g. for unified processing
• CPC Class Codes: H04L 67/568 : Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5681 : Pre-fetching or pre-delivering data based on network characteristics
• CPC Class Codes: H04L 69/16 : Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Abstract

Described are methods, systems and computer readable media for distributed and optimized garbage collection of remote and exported object handle links to update propagation graph nodes.

Claims

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.