Introduction “initialize” operation Session class

7.2.5 Session class

7.2.5.1 Introduction

The Session class allows use of interactive sessions between a client and a server, by providing four stateful operations named “initiate”, “close”, “status”, and “cancel”. This class encapsulates the operations pertaining to session management. This class has an optional association from the Catalogue Service class, in which case this class is implemented by the Catalogue Service implementation. NOTE The four Session operations are patterned after similar Z39.50 services.

7.2.5.2 “initialize” operation

The “initialize” operation is used to establish a session context with a Catalogue Service and is more completely specified in Table 24. provides a UML model of the “initialize” operation that shows the complete Session class with the InitiateRequest and InitiateResponse classes and the class they use. The operation request includes the association role name listed and defined in Table 25. The normal operation response includes the association role name listed and defined in Table 26. Table 24 — Definition of “initiaize” operation Definition Allows clients to initiate an interactive session with a server, and generates a unique identifier used to track the session Receives Identifier of operation request Returns Data describing success or failure of this operation, plus session identifier when successful Exceptions Missing Parameter Value, Invalid Parameter Value Pre-conditions Existence of a Catalogue Service instance that supports sessions Post-conditions Result document returned to requesting client 44 Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved. Figure 10 — “initialize” operation UML static model Table 25 — UML role name in “initialize” operation request Name Definition Data type Optionality and use sessionInfo The core set of parameters required in each message exchanged between a client and server operating in a session context, where these parameters support message routing and session management SessionInfo, See Table 12 Zero or one Conditional Include when sessions are supportedrequired by protocol binding andor result sets are persistent Table 26 — UML role name in “initiaize” operation normal response Name Definition Data type Optionality and use sessionInfo The core set of parameters required in each message exchanged between a client and server operating in a session context, where these parameters support message routing and session management SessionInfo, See Table 12 Zero or one Conditional Include when sessions are supportedrequired by protocol binding andor result sets are persistent NOTE This general model assumes that operation failure will be signalled to the client in a manner specified by each protocol binding.

7.2.5.3 “close” operation