Kbase P101091: 4GL/ABL: Do both the client session and the AppServer session see the a SUPER-PROCEDURE run at the
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/29/2009 |
|
Status: Verified
GOAL:
4GL/ABL: Do both the client session and the AppServer session see the a SUPER-PROCEDURE run at the start of a STATE-AWARE AppServer session?
GOAL:
When a 4GL SUPER-PROCEDURE is run at start up in a STATE-AWARE AppServer, do both the 4GL client application session and the AppServer session see that procedure?
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
FIX:
No, 4GL SUPER-PROCEDURE is scoped to its own session. An AppServer and its 4GL client application run in two separate sessions. Essentially, this means that they have no context in common. Although both the 4GL client and the AppServer run in separate processes, they both run Progress sessions in which some context is exchanged using a common 4GL mechanism.
These two sessions maintain a clear separation of context: persistent procedures, transactions, database connections, AppServer connections, and database trigger events are separately scoped and operate only in the session in which they are invoked.
There is a processing boundary between the two sessions. Only remote procedure requests can break through this processing boundary. A 4GL client invokes these requests using the RUN statement and the CONNECT( ) and DISCONNECT( ) methods on a server object handle.