Transaction management in a configuration database
June 29, 2018. Estimated Expiration Date is calculated based on simple USPTO term provisions. It does not account for terminal disclaimers, term adjustments, failure to pay maintenance fees, or other factors which might affect the term of a patent.Patent ReferencesCommunications network state and topology monitor System for selectively registering and blocking requests initiated by optimistic and pessimistic transactions respectively for shared objects based upon associated locks Network concurrency control for autonomous databases featuring independent lock release and lock ownership transfer Method for authenticating messages passed between tasks Method and apparatus for establishing communications sessions in a remote resource control environment Intelligent real-time graphic-object to database linking-actuator for enabling intuitive on-screen changes and control of system configuration Distributing system configuration information from a manager machine to subscribed endpoint machines in a distrubuted computing environment Global mount mechanism used in maintaining a global name space utilizing a distributed locking mechanism Patent #: 5946685 InventorsApplicationNo. 107043 filed on 06/29/1998US Classes:707/100, DATABASE SCHEMA OR DATA STRUCTURE707/104.1Application of database or data structure (e.g., distributed, multimedia, image)ExaminersPrimary: Alam, Hosain T.Assistant: Shah, Sanjiv Attorney, Agent or FirmForeign Patent References
International ClassG06F 015/00AbstractA method and system are disclosed for updating and managing a configuration database used to store configuration and user data in a computer network having multiple clients, such as network computers. The transaction management mechanisms described determine whether new data, such as a new user or specific property, is being added to the configuration database or whether an existing node in the database is being modified by a transaction. A locking mechanism obtains a lock on a node according to whether a new node is being added to the configuration database or an existing node is being modified. During this process, an identifier is assigned to the transaction that caused the lock that acts as a transaction handle. The transaction then proceeds to modify the configuration database by either adding new data or modifying existing data. The locking mechanism then commits the transaction by releasing the lock if the modification or insertion is successful, or aborts the transaction if the modification or insertion fails.Other References
| |
