Confirmed users
496
edits
Line 37: | Line 37: | ||
In this protocol description, a "request" is a packet sent from the client which always elicits a single packet from the recipient, the "reply". These terms indicate a simple pattern of communication: at any given time, either the client or actor is permitted to send a packet, but never both. | In this protocol description, a "request" is a packet sent from the client which always elicits a single packet from the recipient, the "reply". These terms indicate a simple pattern of communication: at any given time, either the client or actor is permitted to send a packet, but never both. | ||
The client's communication with each actor is treated separately: a client may send a request to one actor, and then send a request to | The client's communication with each actor is treated separately: a client may send a request to one actor, and then send a request to a different actor before receiving a reply from the first. | ||
Packets not described as "requests" or "replies" are part of some more complicated interaction, which should be spelled out in more detail. | Packets not described as "requests" or "replies" are part of some more complicated interaction, which should be spelled out in more detail. |