Building Distributed
Applications
Using the Progress AppServer


Remote Persistent Procedure Handles

When a 4GL client application executes a remote persistent procedure, two persistent procedure handles are created: one within the client application session and another separate handle within the AppServer session where the persistent procedure is created. Progress internally maintains a mapping between the two handles. The handle within the client application is a proxy persistent procedure handle, and its PROXY attribute and PERSISTENT attribute are set to TRUE. The corresponding handle within the Application Server process is a remote persistent procedure handle, and its REMOTE attribute and PERSISTENT attribute are set to TRUE.

Unlike the values of persistent procedure handles and the THIS-PROCEDURE handle that reference the same local procedure context, the proxy persistent procedure handle and the remote persistent procedure handle are truly separate handles. For example, setting the PRIVATE-DATA attribute on a remote persistent procedure handle has no effect on the PRIVATE-DATA attribute of the corresponding proxy persistent procedure handle in the client application.

For more information on the relationship between remote and proxy persistent procedure handles, see the information on procedure handles in Design and Implementation Considerations."


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