WebSpeed
Developer’s Guide


Distributed Applications

When a requesting application with an active transaction runs a remote procedure, Progress does not propagate the transaction to the remote procedure. Rather, the remote procedure acts as if it is the first procedure of the application, and follows the normal SpeedScript rules for starting and terminating transactions. If a requesting application and a remote procedure connect to the same database, each database connection comprises a separate transaction.

For more information on remote procedures, see Building Distributed Applications Using the Progress AppServer.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095