Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rochester!rutgers!mtune!whuts!paul
From: paul@whuts.UUCP (HO)
Newsgroups: comp.dcom.lans,comp.protocols.tcp-ip
Subject: Re: Streams TCP/IP
Message-ID: <2514@whuts.UUCP>
Date: Wed, 29-Jul-87 15:19:10 EDT
Article-I.D.: whuts.2514
Posted: Wed Jul 29 15:19:10 1987
Date-Received: Sat, 1-Aug-87 01:44:08 EDT
References: <725@hjuxa.UUCP> <649@houxa.UUCP>
Organization: AT&T Bell Laboratories
Lines: 15
Keywords: TCP/IP, Streams
Xref: mnetor comp.dcom.lans:700 comp.protocols.tcp-ip:756

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 this just another sales-hype buzzword?  or is there
> a reason Streams is better?  than sockets?  than psudo-sockets? or
> select?  Does the end user see any advantage?  faster response?  less
> CPU waste?  what?  Does anyone have some before & after figures on
> drivers that were converted to Streams?  Please share them with us.

Chapter 10 of the Bach book (The Design of the UNIX Operating System) has
a pretty good discussion and description on STREAMS. Also, Bach and 
others have also written some papers on the SVR3 STREAMS implementation, 
which differs slightly from the Research STREAMS.

	Paul Ho