Conversation states indicate the status
of each side of a conversation. Application programmers on different
processors use conversation states to discuss how their TPs will
communicate. Certain intrinsics (or verbs, depending on the implementation)
can be called from each state, and control information is exchanged
through parameters of the intrinsics. Control information sent by
the remote TP may determine the state of the local side of the conversation.
This chapter defines all the possible states of a conversation
and explains how the various intrinsics affect these states. The
possible states of a conversation are listed in Table 4-1 “Conversation States”.
Table 4-1 Conversation States
State | Meaning |
|---|
Reset | The TP can allocate a mapped conversation. |
Send | The TP can send data or request confirmation. |
Receive | The TP can receive information from the
remote TP. |
Confirm | The TP can reply to a confirmation request
and enter or reenter Receive state. |
Confirm Send | The TP can reply to a confirmation request
and enter Send state. |
Confirm Deallocate | The TP can reply to a confirmation request
and enter Deallocate state. |
Deallocate | The TP can Deallocate the mapped conversation
locally. |
