Lines Matching refs:message

31 struct message {
40 Receipt of an invalid message header, corrupt message payload, or an
43 message stream will result in state getting out of sync.
45 The following sections describe the six defined message types in
51 *sender* of the message, so for a receiver, the meanings are effectively
60 The CONNECT message establishes the presence of a remote system.
62 declares the maximum message body size that the remote system
70 Both sides send a CONNECT message when the connection between them is
71 established.  Until a CONNECT message is received no other messages may
72 be sent. Any messages received before a CONNECT message MUST be ignored.
74 If a CONNECT message is received with an unknown version or insufficiently
87 The AUTH message informs the recipient that authentication is required to
107 The OPEN message informs the recipient that the sender has a stream
109 destination in the message payload.  The local-id may not be zero.
111 The OPEN message MUST result in either a READY message indicating that
113 a CLOSE message, indicating failure.  An OPEN message also implies
114 a READY message sent at the same time.
131 The READY message informs the recipient that the sender's stream
137 A READY message containing a remote-id which does not map to an open
139 closed while this message was in-flight.
141 The local-id is ignored on all but the first READY message (where it
150 The WRITE message sends data to the recipient's stream identified by
153 A WRITE message containing a remote-id which does not map to an open
155 closed while this message was in-flight.
157 A WRITE message may not be sent until a READY message is received.
158 Once a WRITE message is sent, an additional WRITE message may not be
159 sent until another READY message has been received.  Recipients of
160 a WRITE message that is in violation of this requirement will CLOSE
168 The CLOSE message informs recipient that the connection between the
173 A CLOSE message containing a remote-id which does not map to an open
175 already been closed by the recipient while this message was in-flight.
177 The recipient should not respond to a CLOSE message in any way.  The
186 The SYNC message is used by the io pump to make sure that stale
199 --- message command constants ------------------------------------------
224 The endian swapping for the message headers will happen (as needed) in
226 always treat message header values as native-endian.
256 I plan on providing either a message or a special control stream so that
262 message flow that looks like:
266 The far side may choose to issue the READY message as soon as it receives
279 "OKAY" response is sent, otherwise a "FAIL" message is returned.  Once