Abstract: The present invention relates to improvements for managing remote function calls and other mechanisms for managing the remote invocation and control of programs. A separation of the request-driven communication work from one broad unstructured bulk of work into at least two separate portions of management is proposed: a dispatching portion and one or more connection portions. Connections are not closed but are reused whenever advantageous, which yields better performance. A standardized interface is set up which is able to be used by a plurality of different requester applications. Thus, a way is found to pass a RFC connection from one application to another, and the same RFC connection can be used by totally independent applications.

Abstract: The present invention relates to improvements for managing remote function calls and other mechanisms for managing the remote invocation and control of programs. A separation of the request-driven communication work from one broad unstructured bulk of work into at least two separate portions of management is proposed: a dispatching portion and one or more connection portions. Connections are not closed but are reused whenever advantageous, which yields better performance. A standardized interface is set up which is able to be used by a plurality of different requester applications. Thus, a way is found to pass a RFC connection from one application to another, and the same RFC connection can be used by totally independent applications.

Abstract: A system and method for realizing transactions within an existing protocol for accessing information uses control information supported by the protocol for specifying transactional or non-transactional requests. This is achieved by adding controls, e.g. a transaction control and a transaction identifier (ID), to individual requests. The transaction control may be a control for opening or closing a transaction. The transaction ID identifies each individual request belonging to certain transaction. A transaction is opened by a client program by adding a transaction control with a value indicating a new transaction to the first request. Preferably, the server program generates a transaction ID for the opened transaction and sends back a return code containing the transaction ID. All subsequent requests belonging to that transaction are extended with the transaction ID by the client program.