Try OpenEdge Now
skip to main content
Developing AppServer Applications
Programming ABL Client Applications : Managing asynchronous requests
 

Managing asynchronous requests

Asynchronous requests allow an ABL client to execute a remote procedure and continue execution before the AppServer has completed (or even begun) executing the remote request. This mechanism enhances client performance, especially in an event-driven application where the user can continue interacting with the client application while the AppServer processes the remote request.
In the following sections, when executing an asynchronous request, ABL places the request on a send queue for the connection until the AppServer can execute the specified remote procedure. Similarly, when the procedure completes execution, ABL places the results on a response queue, where the results wait until the client handles the PROCEDURE-COMPLETE event associated with the request. As a result, all asynchronous requests on a connection are guaranteed to be executed, with results returned, in the order you submit them. For more information on the send and response queues, see AppServer and Client Interaction.
* Executing an asynchronous request
* Handling the response from an asynchronous request
* Cancelling asynchronous requests
* Cancelling asynchronous requests after a specified time limit
* Asynchronous requests and persistent procedures
* Deleting asynchronous remote persistent procedures
* Deleting server handles
* Deleting asynchronous request handles
* Debugging asynchronous requests
* Mixing synchronous and asynchronous requests
* Running asynchronous requests on the SESSION system handle
* Examples