Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site umich.UUCP
Path: utzoo!linus!decvax!bellcore!petrus!sabre!zeta!epsilon!mb2c!umich!buz
From: buz@umich.UUCP (Greg Buzzard)
Newsgroups: net.unix-wizards,net.lan
Subject: Re: STREAMS query
Message-ID: <261@umich.UUCP>
Date: Tue, 8-Oct-85 02:13:53 EDT
Article-I.D.: umich.261
Posted: Tue Oct  8 02:13:53 1985
Date-Received: Thu, 10-Oct-85 06:49:39 EDT
References: <471@enmasse.UUCP> <1699@brl-tgr.ARPA> <449@cheviot.uucp> <169@ihnp3.UUCP>
Reply-To: buz@eecs.UUCP (Greg Buzzard)
Distribution: net
Organization: U. Mich. -- EECS Dept.
Lines: 13
Keywords: connection oriented, connectionless messages
Xref: linus net.unix-wizards:12317 net.lan:920
Summary: 

Can anybody provide a summary of all the *different* contexts in which
the term "stream", or "stream service", etc. is used?
I suspect that "stream", "stream service", etc.  probably fit into
that class of terms that are sufficiently overused so as to have
several (well, at least two) different context dependent meanings.

For instance, I generally consider "stream service" to imply a
protocol that (unless explicitly stated otherwise is end-to-end
reliable, i.e., guarantees delivery, eliminates duplicates, and...) 
appears as a uni-directional device interface (such as a printer,
or sensor) which cannot be backspaced or reread and for which no
explicit synchronization exists.  Is this inconsistent with the
standard Unix(?) concept of STREAM?