Rules for Flushing Queues
The following rules pertain to flushing the stream queues.
No other flushes should be needed to keep the queues in the proper condition.
-
The transport providers must be aware that they will receive
M_FLUSH
messages from upstream.
These flush requests are issued to ensure that the providers receive certain
messages and primitives.
It is the responsibility of the providers to act appropriately as deemed
necessary by the providers.
-
The transport provider must send up a
M_FLUSH
message to
flush both the read and write
queues after receiving a successful
T_UNBIND_REQ
message and
before issuing the
T_OK_ACK
primitive.
The following rules pertain only to the connection-mode transport providers.
-
If the interface is in the
T_DATA_XFER,
T_WIND_ORDREL
or
T_WACK_ORDREL
state, the
transport provider must send up a
M_FLUSH
message to
flush both the read and write
queues before sending up a
T_DISCON_IND.
-
If the interface is in the
T_DATA_XFER,
T_WIND_ORDREL
or
T_WACK_ORDREL
state, the
transport provider must send up a
M_FLUSH
message to
flush both the read and write
queues after receiving a successful
T_DISCON_REQ
message and before
issuing the
T_OK_ACK
primitive.
© 2005 The SCO Group, Inc. All rights reserved.
OpenServer 6 and UnixWare (SVR5) HDK - June 2005