Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!husc6!seismo!mcvax!ukc!its63b!adam
From: adam@its63b.UUCP
Newsgroups: comp.dcom.lans
Subject: Re: Streams vs. Sockets
Message-ID: <268@its63b.ed.ac.uk>
Date: Mon, 23-Feb-87 06:01:30 EST
Article-I.D.: its63b.268
Posted: Mon Feb 23 06:01:30 1987
Date-Received: Fri, 27-Feb-87 22:23:29 EST
References: <605@rna.UUCP>
Reply-To: adam@its63b.ed.ac.uk (ERCF02 Adam Hamilton)
Organization: I.T. School, Univ. of Edinburgh, U.K.
Lines: 11


	Some care is needed here when making this comparison.
"Sockets" are really a user level interface to networking code.
Streams are an implementation method for networking code.
Therefore they are not strictly comparable.  If you doubt this, reflect
that one could implement the socket interface with stream-based modules.

"Sockets" is also taken to mean the well-known implementation of this
interface that we all know and love.  You can compare this to streams.

		Adam Hamilton