Streams Vs Sockets

[Richard Wolski]

I have a question regarding AT&T streams vs. BSD sockets as interfaces
for networking under UNIX.  Specifically, my site uses both 4.X BSD
systems and System V computers, and I am looking for a single clean
way to integrate a locally developed networking protocol called LINCS.

I realize the System V and the Berkeley distributions are different
animals, and that the natural answer is to use streams for the
V.3 systems, and sockets for the BSD machines.  What I am ultimately
after is a single interface which then could be ported to all of the
UNIX machines here at the labs.

For example, if streams turn out to be a better choice for networking
than sockets, and the V.3 licensing agreement is not violated, we could
port the stream code to our 4.X machines and then install LINCS.  On the
other hand, I have heard that there exists socket code for System V 
machines which we could port to all of our AT&T based equipment to use
as an interface.

I guess what I am asking for is arguments for and/or against streams,
sockets, or any permutation there of, as well as any advice on the subject
which might be of use (i.e. the names of books, documents, etc. where
I could get more information).

Thank you all in advance,
Richard Wolski

a tourist in Technical Disneyland

rwolski at lll-lcc		arpa
ihnp4!lll-lcc!rwolski	uucp