[Next] [Up] [Previous] [Contents]
Next: 4.1.28 Which instance manages Up: 4.1 General Previous: 4.1.26 Does a new

4.1.27 Will the current context be valid for all requests of the client (and all replies of the server) till the client decides that the context is not valid anymore?

 

Jonathan Biggar
(July, 1998) : Not necessarily. I believe that a server is allowed to signal to the client that a context is no longer valid, which means the client must reestablish a new context. Also, it is possible for a single server to manage objects in different security domains that may require more than one context be established to the server from a single client.
Nick Battle
(July, 1998) : The context is certainly long lived (more than one invocation) - this is a matter of efficiency, since session key establishment is typically very expensive. The context can be destroyed by either peer (eg. by deleting the object or its object reference) or it can timeout. The lifetime is a matter of policy (and cannot be increased by the peers). Contexts may also be destroyed as part of handling a SECIOP protocol error.


[Next] [Up] [Previous] [Contents]
Next: 4.1.28 Which instance manages Up: 4.1 General Previous: 4.1.26 Does a new