Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!ICO.ISC.COM!dougm
From: dougm@ICO.ISC.COM ("Doug McCallum")
Newsgroups: comp.protocols.tcp-ip
Subject: Re(2): Re: Sockets vs streams.  An attempt to answer the original question
Message-ID: <9008291444.AA15182@violet.ICO.ISC.COM>
Date: 29 Aug 90 14:44:46 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 20

In reply to your message of 29 August 1990 0643-PDT (Wednesday)
-------
> Anybody know what tirdwr does?  Gather/scatter packets to satisfy
> the read/write size argument?  Some oob handling?

All tirdwr does is get rid of the protocol part of the TLI (actually TPI)
messages.  Read/write can only deal with what are called M_DATA messages.
The protocol between TLI and TPI (Transport Provider Interface) has another
message block type (M_PROTO) in front of the data.  It also interprets
disconnects.  Anything else, like an expedited data message (T_EXDATA_IND)
is a fatal error.

> ps. Is there anyway to get a list of all the modules pushed onto
> a stream.  I_LOOK only lists the top most module.

Not in V.3.

Doug McCallum
Interactive Systems Corp.
dougm@ico.isc.com