close

With tirdwr on a Stream, the user can send and receive data over a transport connection for the duration of that connection. Either user may terminate the connection by closing the file descriptor associated with the transport endpoint or by popping the tirdwr module off the Stream. In either case, tirdwr will take the following actions:

• If tirdwr previously received an orderly release indication, it will pass an orderly release request to the transport provider to complete the orderly release of the connection. The remote user who initiated the orderly release procedure will receive the expected indication when data transfer completes.

• If tirdwr previously received a disconnect indication, it does not take any special action.

• If tirdwr did not previously receive an orderly release indication or a disconnect indication, it will pass a disconnect request to the transport provider to abort the connection.

• If an error previously occurred on the Stream and tirdwr has not received a disconnect indication, it will pass a disconnect request to the transport provider.

A process may not initiate an orderly release after tirdwr is pushed onto a Stream, but tirdwr will handle an orderly release properly if it is initiated by the user on the other side of a transport connection. If the client in this section is communicating with the server program in ``Connection-mode service'', that server will terminate the transfer of data with an orderly release request. The server then waits for the corresponding indication from the client. At that point, the client exits and the transport endpoint is closed. As explained in the first list item above, when the file descriptor is closed, tirdwr will initiate the orderly release request from the client's side of the connection. This will generate the indication that the server is expecting, and the connection will be released properly.