Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!usc!samsung!uunet!auspex!guy From: guy@auspex.auspex.com (Guy Harris) Newsgroups: comp.protocols.tcp-ip Subject: Re: Sockets vs streams. An attempt to answer the original question Message-ID: <3973@auspex.auspex.com> Date: 28 Aug 90 20:05:05 GMT References: <1990Aug27.111656.1@amazon.llnl.gov> Organization: Auspex Systems, Santa Clara Lines: 20 >The real issue seems to be not this, but the problem that streams >doesn't fit the normal Unix view of I/O. At least in SunOS 4.1, you >can't do read and write on a stream. Well, yes, you can, actually. You have programs that do "read()" and "write()" on terminals under SunOS 4.x, right? If so, they're doing "read()" and "write()" on streams.... What you can't do in SunOS 4.1 - nor in the S5R3 systems from which much of that code came - is "read()" and "write()" on *TLI* streams that don't have the "tirdwr" module pushed atop them. That module, which you mention, actually comes from S5R3. In S5R[34], streams isn't really the equivalent of sockets, streams *plus TLI* is. (I wouldn't be at all surprised to find that in the Research UNIX streams code, you *can* do "read()" and "write()" on streams used for network connections. I don't know if this is the case, but I wouldn't be surprised if it were....) Brought to you by Super Global Mega Corp .com