...
Endpoint objects are created in one of two scenarios. In the most basic case the local application directly triggers creation of an endpoint object in order to initiate the given type of conversation (Connection, Session, or Link). In other cases thoughthe case of Sessions and Links, the remote application might trigger the engine to internally create a Session or Link endpoint, but not a Connection endpointan endpoint. The local and last known remote endpoint state may be used to distinguish between the various scenarios. In total there are 9 possible combinations of these states described in more detail in the table below.
Local | Remote | Description |
---|---|---|
UNINIT | UNINIT | This would be the initial state of an endpoint that is newly created by the local application. |
UNINIT | ACTIVE | This would be the initial state of an endpoint that was created by the engine in response to actions taken by the remote application.It can be thought of as "half open". |
UNINIT | CLOSED | Same as the above except the remote application has chosen to close its own endpoint prior to reaching a fully established state, i.e. the remote application is aborting. |
ACTIVE | UNINIT | Locally initiated "half open". |
ACTIVE | ACTIVE | Pairing between the two endpoints is fully established. |
ACTIVE | CLOSED | In the process of a remotely initiated closing. (Half closed). |
CLOSED | UNINIT | In the process of a locally initiated abort. |
CLOSED | ACTIVE | In the process of a locallly initiated closing. (Half Closed) |
CLOSED | CLOSED | Fully closed. |
...
Deliveries
Gliffy Diagram | ||
---|---|---|
|
...