Abstract: Threads of a multithreaded client application access data in one or more global data repositories via one or more local trees. Each local tree is associated with one or more locked resources of the global data repository. By using the local trees in accessing the data of the global repository, a thread is automatically associated with a lock block and therefore, the granting of locks is independent of any threading models.

Abstract: The management and use of replicated distributed transactions is facilitated. A distributed synchronous transaction system protocol is provided to manage the replication of distributed transactions for client application instances. The distributed synchronous transaction system allows transactions to be replicated without having the client application instances be aware of other instances to receive the transaction. Further, if a failure occurs during processing of a distributed replicated transaction, the distributed synchronous transaction system manages the recovery of the failure.

Abstract: The management and use of replicated distributed transactions is facilitated. A distributed synchronous transaction system protocol is provided to manage the replication of distributed transactions for client application instances. The distributed synchronous transaction system allows transactions to be replicated without having the client application instances be aware of other instances to receive the transaction. Further, if a failure occurs during processing of a distributed replicated transaction, the distributed synchronous transaction system manages the recovery of the failure.

Abstract: A structure and method are provided which can model and use information in a systematic, domain-independent manner, which can flexibly represent declarative data such as concepts, instances, relations and contexts and data views, and which may serve as a middleware module for user applications. The invention teaches a syntax and functionality of a set of software objects that represent, store and dynamically retrieve information on behalf of user applications.

Abstract: A method (and structure) to retrieve data from information structures based on an entity/relation paradigm and characterized as being a self-similar hypergraph, includes creating a template that matches a self-similar hypergraph format of the information structure. The template contains at least one query unit.

Abstract: A method (and structure) for using reasoning heuristics in a network-based information system based on an entity/relation paradigm and characterized as being a self-similar hypergraph. The method includes packaging domain-independent reasoning heuristics so that they can be attached to data in a self-similar-hypergraph information system, thereby allowing self-describing knowledge capsules to be created from the data.

Abstract: At least a portion of a table stored in a global data repository is selected to be accessed and modified. The selected portion is stored in a local table in local memory of a node of a client-server environment. The local table is modified, and then at least a portion of the modified local table is merged with the global table. The merger is performed without requiring any user locking of the global table.

Abstract: One or more tables stored in a global data repository are concurrently accessible and modifiable. A client requests the locking of one or more tables within a global server data repository on behalf of a local tree. This locking creates a lock block, which enables at least a portion of the locked tables to be selected, modified and then merged back with the tables residing in the server. One or more other clients may also request to use the same lock block and thus, the same local tree, if shared concurrency is allowed. These other clients would also be allowed to select, modify and merge at least a portion of the tables. The merging of the tables is serialized at the global data repository, if necessary.

Abstract: Write requests are performed against one or more resources of a resource group in a persistent and atomic manner. When a write request is received, a backup resource group is updated to reflect data in a current resource group. Thereafter, the write request is performed against the backup resource group. After successfully performing the write operation(s), the backup resource group and the current resource group are swapped in an atomic, consistent manner, such that the backup resource group is now the new current resource group.