Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!ucbvax!NPRDC.NAVY.MIL!stanonik
From: stanonik@NPRDC.NAVY.MIL (Ron Stanonik)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Re: Sockets vs streams.  An attempt to answer the original question
Message-ID: <9008291343.AA04892@atlantic.nprdc.navy.mil>
Date: 29 Aug 90 13:43:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: stanonik@nprdc.navy.mil
Organization: The Internet
Lines: 13

Wollongong's win 3b implementation of tcp/ip (on our 3b2's running
sysVr3) seems to only push tirdwr for the accept socket call.  We've
installed a couple of bsd programs (syslog and lpr), which use
read/write and seem to work just fine.

Anybody know what tirdwr does?  Gather/scatter packets to satisfy
the read/write size argument?  Some oob handling?

Ron Stanonik
stanonik@nprdc.navy.mil

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