Abstract: An interface is used to manage nested atomic transactions, in which a transaction participant can also be a transaction manager. These transactions include fundamental and/or composite commands. Each command is represented by a command object, and the interface is implemented by methods and variables in each of these command objects. The interface enables a transaction manager to instruct its transaction participants to perform prepare and commit or rollback phases and to ascertain whether the prepare phases succeed or fail. The interface enables any command object to be a transaction manager and a transaction participant.

Abstract: A method for controlling access to functionality in an application program according to one embodiment includes registering at least one permission set in a database. The permission set includes a plurality of privileged actions relating to a functional category of the application program. The method further includes receiving information granting a principal authorization to at least one of the privileged actions in the permission set, and performing the authorized privileged action in accordance with the received information when initiated by the principal.

Abstract: An interface is used to manage nested atomic transactions, in which a transaction participant can also be a transaction manager. These transactions include fundamental and/or composite commands. Each command is represented by a command object, and the interface is implemented by methods and variables in each of these command objects. The interface enables a transaction manager to instruct its transaction participants to perform prepare and commit or rollback phases and to ascertain whether the prepare phases succeed or fail. The interface enables any command object to be a transaction manager and a transaction participant.