The client side of the C/S Messaging API service fires the following events:
C/S Messaging API events
CSReplyEvent
Signals when an asynchronous send(ClientOperation aClientOperation) request method with the specified aRequestId has finished.
The event instance contains the request identifier (aRequestId) data, which can be obtained using the getRequestId() instance method.
Then, the receiver of the reply event uses either the receive(Context aContext, Integer aRequestId, long timeout) or the receive(ClientOperation aClientOperation, Integer aRequestId, long timeout) method to complete the receive process.
CSStatusChangedEvent
Signals when the session status has changed. The event instance contains as data the session status, which can be obtained using the getSessionStatus() instance method. Possible values for the session status are:
▪ Initial state
▪ Session established
▪ Session is down
▪ Session not established
▪ Session is being closed
It is the responsibility of the registered listener (to the application) to handle the event and perform the behavior required by the application.
CSInactivityClientEvent
Signals when the session has expired due to client inactivity. The event instance contains as data the session ID that has expired, and this can be obtained using the getSessionExpired() instance method.
It is the responsibility of the listener (the application) to handle the event and perform any necessary cleanup.