Method and apparatus for managing transactions in an object-oriented distributed system

Claim 2

In a distributed computing system, having at least one client program and at least one sub-program, each sub-program having an implementor, said system having at least one computer node, and each node having an operating system kernel, a method for managing transactions, performed by a computer, comprising the steps of: providing a Transaction Manager (TM) in each node, said TM comprising mechanisms configured to provide control of transaction assignment, transaction control, and commit and abort voting in object-oriented distributed systems; assigning a transaction identification (TID) value to a request from an originating client program to create a transaction and returning said TID value to the originating client program; the originating client program requesting at least one sub-program to join as a participant in the transaction and passing a copy of said TID value to said at least one participating sub-program; the TM receiving a call-back mechanism from an implementor of said at least one participating sub-program, and returning a transaction voting mechanism to said implementor, thereby establishing a two-way communication path between the TM and the implementor of the at least one participating sub-program; whereby all participating sub-programs may indicate whether said transaction was completed correctly, without any required support of the operating system kernel.

Claim 3

The method of claim 1 wherein said implementors may notify the TM to abort the transaction, without any required support of the operating system kernel.

Claim 4

The method of claim 2 wherein said participating sub-programs and said originating client program can be notified by the TM of the completion status of said transaction, without any required support of the operating system kernel.

Claim 5

The method of claim 3 wherein all programs, sub-programs and implementors are objects.

Claim 6

In an object-oriented distributed computing system, having at least one client program and at least one object, each object having an object implementation, said system having at least one computer node, and each node having an operating system kernel, a method for managing transactions, performed by a computer, comprising the steps of: providing a Transaction Manager (TM) in each node, said TM comprising mechanisms configured to provide control of transaction assignment, transaction control, and commit and abort voting in object-oriented distributed systems; assigning a transaction identification (TID) value to a request from an originating client program to create a transaction and returning a TID object containing said value to the originating client program; the originating client program requesting at least one object to join as a participant in the transaction and passing a copy of said TID object to said at least one participating object; the TM receiving a call-back object from an object implementation of said at least one participating object, and returning a transaction voting object to said object implementation, thereby establishing a two-way communication path between the TM and the object implementation of the at least one participating object; whereby all participating objects may indicate whether said transaction was completed correctly, without any required support of the operating system kernel.

Claim 7

In an object-oriented distributed computing system, having at least one client program and at least one object, each object having an object implementation, said system having at least one computer node, and each node having an operating system kernel, a method for managing transactions, performed by a computer, comprising the steps of: providing a Transaction Manager (TM) in each node, said TM comprising mechanisms configured to provide control of transaction assignment, transaction control, and commit and abort voting in object-oriented distributed systems; assigning a transaction identification (TID) value to a request from an originating client program to create a transaction and returning a TID object containing said value to the originating client program; the originating client program requesting at least one object to join as a participant in the transaction and passing a copy of said TID object to said at least one participating object; the TM receiving a call-back object from an object implementation of said at least one participating object, and returning a transaction voting object to said object implementation, thereby establishing a two-way communication path between the TM and the object implementation of the at least one participating object; whereby all participating objects may indicate whether said transaction was completed correctly, without any required support of the operating system kernel.

Claim 8

The method of claim 5 wherein said object implementations may notify the TM to abort the transaction, without any required support of the operating system kernel.

Claim 9

The method of claim 6 wherein said participating objects and said originating client program can be notified by the TM of the completion status of said transaction, without any required support of the operating system kernel.

Claim 10

The method of claim 5 comprising the additional step of said TM returning a master voting object containing the TID value to said originating client program, in response to the command to create a transaction, whereby said originating client program can query the TM as to the completion status of said transaction without support from said operating system kernel.

Claim 11

The method of claim 5 wherein the step of said TM receiving a call-back object from an object implementation of a participating object results from said object implementation of a participating object invoking the register -- object -- manager command on the TID object, said TM being the object implementation of the TID object.

Claim 12

The method of claim 9 wherein said at least one participating object may be on any of the computer nodes in the distributed computing system.

Claim 13

The method of claim 10 wherein an object implementation of an object participating in said transaction may be on any of the computer nodes in the distributed computing system.

Claim 14

The method of claim 11 wherein objects participating in said transaction inherit from an object of type atomic.

Claim 15

The method of claim 12 wherein said objects which inherit from said object of type atomic are invited to be participants in said transaction by said originating client program by invoking the join -- transaction (TID) call on each of said object of type atomic.

Claim 16

The method of claim 13 wherein said participating objects which have been joined to said transaction may be passed around to other client programs that do not know that operations on these participating objects are part of a transaction.

Claim 17

In an object-oriented distributed computing system, having at least one client program and at least one object, each object having an object implementation, said system having at least one computer node, and each node having an operating system kernel, an apparatus for managing transactions comprising: a Transaction Manager (TM) in each node, said TM comprising mechanisms configured to provide control of transaction assignment, transaction control, and commit and abort voting in object-oriented distributed systems; said TM further comprising mechanisms configured to assign a transaction identification (TID) value to a request from an originating client program to create a transaction and a first communications mechanism configured to return a TID object containing said TID value to the originating client program; a requesting mechanism configured to be used by the originating client program in requesting at least one object to join as a participant in the transaction wherein said request passes a copy of said TID object to said at least one participating object; and a second communications mechanism configured to be used by the TM for receiving a call-back object from an object implementation of said at least one participating object, and for returning a transaction voting object to said object implementation, thereby establishing a two-way communication path between the TM and the object implementation of the at least one participating object; whereby all participating objects may indicate whether said transaction was completed correctly, without any required support of the operating system kernel.

Claim 18

In an object-oriented distributed computing system, having at least one client program and at least one object, each object having an object implementation, said system having at least one computer node, and each node having an operating system kernel, an apparatus for managing transactions comprising: a Transaction Manager (TM) in each node, said TM comprising mechanisms configured to provide control of transaction assignment, transaction control, and commit and abort voting in object-oriented distributed systems; said TM further comprising mechanisms configured to assign a transaction identification (TID) value to a request from an originating client program to create a transaction and a first communications mechanism configured to return a TID object containing said TID value to the originating client program; a requesting mechanism configured to be used by the originating client program in requesting at least one object to join as a participant in the transaction wherein said request passes a copy of said TID object to said at least one participating object; and a second communications mechanism configured to be used by the TM for receiving a call-back object from an object implementation of said at least one participating object, and for returning a transaction voting object to said object implementation, thereby establishing a two-way communication path between the TM and the object implementation of the at least one participating object; whereby all participating objects may indicate whether said transaction was completed correctly, without any required support of the operating system kernel.

Claim 19

The apparatus of claim 15 wherein said object implementations may notify the TM to abort the transaction, without any required support of the operating system kernel.

Claim 20

The apparatus of claim 16 wherein said participating objects and said originating client program can be notified by the TM of the completion status of said transaction, without any required support of the operating system kernel.

Claim 21

The apparatus of claim 15 wherein said TM returns a master voting object containing the TID to said originating client program in addition to said TID object, in response to the command to create a transaction, whereby said originating client program can query the TM as to the completion status of said transaction without support from said operating system kernel.

Claim 22

The apparatus of claim 18 wherein said TM receiving a call-back object from an object implementation of a participating object results from said object implementation of a participating object using said second communications means to register said object implementation with said TM.

Claim 23

The apparatus of claim 19 wherein said at least one participating object may be on any of the computer nodes in the distributed computing system.

Claim 24

The apparatus of claim 20 wherein an object implementation of an object participating in said transaction may be on any of the computer nodes in the distributed computing system.

Claim 25

The apparatus of claim 21 wherein objects participating in said transaction inherit from an object of type atomic.

Claim 26

The apparatus of claim 22 wherein said objects which inherit from said object of type atomic are invited to be participants in said transaction by said originating client program by invoking the join -- transaction (TID) call on each of said objects.

Claim 27

The apparatus of claim 23 wherein said participating objects which have been joined to said transaction may be passed around to other client programs that do not know that operations on these participating objects are part of a transaction.

Claim 28

A computer program product having a computer readable medium having a computer program recorded thereon for managing the processing of transactions invoked by a client application, for use in an object oriented distributed computer system wherein there exists client applications, objects, object type definitions, object implementations and servers, and an operating system kernel, said computer program product comprising: a Transaction Manager (TM) comprising mechanisms configured to provide control of a transaction in object-oriented distributed systems; an assigning program code mechanism for use by a transaction manager (TM) to assign a transaction identification (TID) value to a request from an originating client program to create a transaction and a first communications means for returning a TID object containing said value to the originating client program; a requesting program code mechanism for use by the originating client program in requesting at least one object to join as a participant in the transaction wherein said request passes a copy of said TID object to said at least one participating object; and a second communications mechanism for use by the TM for receiving a call-back object from an object implementation of said at least one participating object, and for returning a transaction voting object to said object implementation, thereby establishing a two-way communication path between the TM and the object implementation of the at least one participating object; whereby all participating objects may indicate whether said transaction was completed correctly, without any required support of the operating system kernel.

Claim 29

A computer program product having a computer readable medium having a computer program recorded thereon for managing the processing of transactions invoked by a client application, for use in an object oriented distributed computer system wherein there exists client applications, objects, object type definitions, object implementations and servers, and an operating system kernel, said computer program product comprising: a Transaction Manager (TM) comprising mechanisms configured to provide control of a transaction in object-oriented distributed systems; an assigning program code mechanism for use by a transaction manager (TM) to assign a transaction identification (TID) value to a request from an originating client program to create a transaction and a first communications means for returning a TID object containing said value to the originating client program; a requesting program code mechanism for use by the originating client program in requesting at least one object to join as a participant in the transaction wherein said request passes a copy of said TID object to said at least one participating object; and a second communications mechanism for use by the TM for receiving a call-back object from an object implementation of said at least one participating object, and for returning a transaction voting object to said object implementation, thereby establishing a two-way communication path between the TM and the object implementation of the at least one participating object; whereby all participating objects may indicate whether said transaction was completed correctly, without any required support of the operating system kernel.

Claim 30

The computer program product of claim 25 wherein said object implementations may notify the TM to abort the transaction, without any required support of the operating system kernel.

Claim 31

The computer program product of claim 26 wherein said participating objects and said originating client program can be notified by the TM of the completion status of said transaction without any required support from the operating system kernel.

Claim 32

The computer program product of claim 27 wherein the TM has the ability to return a master voting object containing the TID to said originating client program in addition to said TID object, in response to the command to create a transaction, whereby said originating client program can query the TM as to the completion status of said transaction without support from said operating system kernel.

Claim 33

The computer program product of claim 28 wherein said TM has the ability to receive said call-back object from an object implementation of a participating object when said object implementation of a participating object uses said second communications means to register said object implementation with said TM.

Claim 34

The computer program product of claim 29 wherein said at least one participating object may be on any computer node in said distributed computing system.

Claim 35

The computer program product of claim 30 wherein an object implementation of an object participating in said transaction may be on any computer node in said distributed computing system.

Claim 36

The computer program product of claim 31 wherein objects participating in said transaction inherit from an object of type atomic.

Claim 37

The computer program product of claim 32 wherein said objects which inherit from said object of type atomic are invited to be participants in said transaction by said originating client program by invoking the join -- transaction (TID) call on each of said objects.

Claim 38

The computer program product of claim 33 wherein said participating objects which have been joined to said transaction may be passed around to other client programs that do not know that operations on these participating objects are part of a transaction.

Claim 39

A computer program product having a computer readable medium having a computer program recorded thereon for managing the processing of transactions invoked by a client application, for use in a distributed computer system wherein there exists client applications programs, sub-programs, implementors, and an operating system kernel, said computer program product comprising: a Transaction Manager (TM) comprising mechanisms configured to provide control of a transaction in object-oriented distributed systems; an assigning program code means for use by a transaction manager (TM) to assign a transaction identification (TID) value to a request from an originating client program to create a transaction and a first communications means for returning said TID value to the originating client program; a requesting program code means for use by the originating client program in requesting at least one sub-program to join as a participant in the transaction wherein said request passes a copy of said TID value to said at least one participating sub-program; and a second communications means for use by the TM for receiving a call-back mechanism from an implementor of said at least one participating sub-program, and for returning a transaction voting mechanism to said implementor, thereby establishing a two-way communication path between the TM and the implementor of the at least one participating sub-program; whereby all participating sub-programs may indicate whether said transaction was completed correctly, without any required support of the operating system kernel.

Claim 40

A computer program product having a computer readable medium having a computer program recorded thereon for managing the processing of transactions invoked by a client application, for use in a distributed computer system wherein there exists client applications programs, sub-programs, implementors, and an operating system kernel, said computer program product comprising: a Transaction Manager (TM) comprising mechanisms configured to provide control of a transaction in object-oriented distributed systems; an assigning program code means for use by a transaction manager (TM) to assign a transaction identification (TID) value to a request from an originating client program to create a transaction and a first communications means for returning said TID value to the originating client program; a requesting program code means for use by the originating client program in requesting at least one sub-program to join as a participant in the transaction wherein said request passes a copy of said TID value to said at least one participating sub-program; and a second communications means for use by the TM for receiving a call-back mechanism from an implementor of said at least one participating sub-program, and for returning a transaction voting mechanism to said implementor, thereby establishing a two-way communication path between the TM and the implementor of the at least one participating sub-program; whereby all participating sub-programs may indicate whether said transaction was completed correctly, without any required support of the operating system kernel.

Claim 41

The computer program product of claim 35 wherein said implementors may notify the TM to abort the transaction, without any required support of the operating system kernel.

Claim 42

The computer program product of claim 36 wherein said participating sub-programs and said originating client program can be notified by the TM of the completion status of said transaction without any required support of the operating system kernel.

Claim 43

The method of claim 3 comprising the additional step of said TM returning a master voting mechanism containing the TID value to said originating client program, in response to the command to create a transaction, whereby said originating client program can query the TM as to the completion status of said transaction without support from said operating system kernel.

Claim 44

The method of claim 38 comprising the additional step of invoking a create sub-transaction call on one of said transaction voting mechanisms whereby a nested transaction is created.

Claim 45

The method of claim 5 comprising the additional step of invoking a create sub-transaction call on one of said transaction voting objects whereby a nested transaction is created.

Claim 46

The apparatus of claim 15 further comprising invoking means for invoking a create sub-transaction call on one of said transaction voting objects whereby a nested transaction is created.

Claim 47

The computer program product of claim 25 further comprising a program code means for invoking a create sub-transaction call on one of said transaction voting objects whereby a nested transaction is created.