...
| 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
In addition to holding the common endpoint state described above, Link endpoints also track the state of messages in the process of being transferred between a designated Source and Target. Each message transfer is associated with a Delivery object, and the Link endpoint internally keeps an ordered set of these objects. Depending on the directionality of the given Link endpoint (Receiver vs Sender), the Deliveries are kept in either incoming or outgoing order.
| Gliffy Diagram |
|---|
| name | Link-Delivery Object Diagram |
|---|
|
Messenger
...