STREAMS-based Transport Provider Interface

Precedence of TPI Primitives on a Stream

The following rules apply to the precedence of transport interface primitives with respect to their position on a stream:

NOTE: The stream queue which contains the transport user initiated primitives is referred to as the stream write queue. The stream queue which contains the transport provider initiated primitives is referred to as the stream read queue.

The transport provider has responsibility for determining precedence on its stream write queue, as described in the rules in ``Transport Primitive Precedence''. This section specifies the rules for precedence for both the connection-mode and connectionless-mode transport services.
The transport user has responsibility for determining precedence on its stream read queue, as described in the rules in ``Transport Primitive Precedence''.
All primitives on the stream are assumed to be placed on the queue in the correct sequence as defined above.

The following rules apply only to the connection-mode transport services.

There is no guarantee of delivery of user data once a T_DISCON_REQ primitive has been issued.