Lines Matching full:messages

156 which should be used for data and messages received through that hook
166 Two types of information flow between nodes: data messages and
167 control messages.
168 Data messages are passed in
179 Along with data, nodes can also receive control messages.
180 There are generic and type-specific control messages.
181 Control messages have a common
192 generic control messages below).
222 Messages often represent commands that are followed by a reply message
232 Typically each type defines a unique typecookie for the messages
235 implement more than one type of messages.
245 messages for flow control and link management purposes are
254 That is, data and control messages are delivered by making function
549 All control messages and replies are
559 Messages must be freed using the
565 messages, and status change messages, where the node may want to forward
569 for messages received on a particular hook, to simplify coding.
574 other than it will receive all (and only) messages from that hook.
658 .Em control messages .
663 This allows the option of hop-by-hop distribution of messages and
665 Data messages are
675 In a similar way, flow control messages may be routed in the reverse
682 which might decide to send similar messages to both nodes
686 addressing to route the messages.
816 messages received on the hook on which they are set.
840 Control messages have the following structure:
865 Control messages have the fixed header shown above, followed by a
893 argument format, and cookie for its own messages.
910 a corresponding set of generic messages which all nodes understand.
911 The handling of these messages is automatic.
922 Some modules may choose to implement messages from more than one
925 Control messages are in binary format for efficiency.
928 it, control messages may be converted to and from an equivalent
994 .Ss Generic Control Messages
995 There are a number of standard predefined messages that will work
999 along with the basic layout of messages and other similar information.
1076 A node will typically only know how to translate messages that it
1099 .Ss Flow Control Messages
1100 In addition to the control messages that affect nodes with respect to the
1103 messages defined.
1108 flow control, and will be in the likely path of these messages.
1109 The default action of a node that does not understand these messages should
1112 These messages are also defined in
1185 socket is used for sending and receiving control messages.
1186 Data and control messages are passed using the
1194 Responds only to generic messages and is a
1200 Responds only to generic messages and always echoes data back through the
1202 Returns any non-generic messages as their own response.
1323 All data messages are
1338 Messages sent using one of
1345 Both control messages and data are delivered and queued with a
1361 messages.