Class Session {Analysis}

Documentation
This class provides capabilities to manage the client-server connection. Its main purpose is to enable either a client or server to detect the loss of communication with the associated party.
For a single communication session between a NMS and an EMS, there are two Session class instances. One is maintained on the NMS; the other one is maintained on the EMS.
Each Session class instance is responsible to "ping" the other Session periodically to detect communication failures. Exactly when this is done is up to the implementation.
When a Session class instance detects a communication failure, or when the endSession operation is called on it, all resources allocated with that communication session must be released and the Session class instance must be deleted.
Object Lifecycle: NA
Object Creation Notification Issued? NA
Object Deletion Notification Issued? NA

Parent Package | Logical View | Abstract | Yes
Export Control | PublicAccess | Link Class for | None
Class Kind | NormalClass | Cardinality | n
Space |  | Concurrency | Sequential
Persistence | No |  |

Operations

Name | Signature | Class
ping | void ping () | Session
endSession | void endSession () | Session

Associations

Name | My Role | My Class | Other Role | Other Element
--Not Named-- | associatedSession | Session | --Not Named-- | Session