Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!gatech!hao!ames!oliveb!amdahl!unixprt!monkey From: monkey@unixprt.UUCP (Monkey Face@unixprt) Newsgroups: comp.dcom.lans,comp.protocols.tcp-ip Subject: Re: Streams TCP/IP Message-ID: <278@unixprt.UUCP> Date: Thu, 23-Jul-87 01:57:54 EDT Article-I.D.: unixprt.278 Posted: Thu Jul 23 01:57:54 1987 Date-Received: Sat, 25-Jul-87 06:41:13 EDT References: <725@hjuxa.UUCP> <649@houxa.UUCP> Organization: uni-xperts - Unix System and Networking Consultants Lines: 23 Keywords: TCP/IP, Streams Summary: Streams advantages/disadvantages Xref: mnetor comp.dcom.lans:680 comp.protocols.tcp-ip:675 In article <649@houxa.UUCP>, mel1@houxa.UUCP (M.HAAS) writes: > Would someone please post a summary of reasons why use of Streams is > an advantage... is there a reason Streams is better? than sockets?... > Does the end user see any advantage?... > Thanks, > Mel Haas , odyssey!mel First it is STREAMS, as apposed to Streams, streams, this differenciates it from a stream based environment. The primary advantage, for those using ATT based UNIX, is that this is the only 'real' facility provided in UNIX System V to support networking. It basically provides the 'structure' that allows layered protocols a consistent interface to other layers in a somewhat independent manner. It is not necessarily 'better', but it is a more appropriately structure for the varying protocols than other implementations (such as the 4.x BSD architecture). Hopefully the 'end-user' doesn't get involved at this level. ATT's Transport Interface is mostly base on the ISO transport interface, therefore should map to the emerging interface standards. I have found that performance is not considerably different in s STREAMS based vs. 4.x BSD based implemetnation of TCP/IP. Monkey Face - uni-xperts