Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!ulysses!hector!ekrell
From: ekrell@hector.UUCP (Eduardo Krell)
Newsgroups: comp.unix.questions
Subject: Re: UNIX System V Release n
Keywords: UNIX System V Release 4.0 Multics complexity kludge
Message-ID: <10968@ulysses.homer.nj.att.com>
Date: 7 Dec 88 04:01:27 GMT
References: <422@ubbpc.UUCP> <9089@smoke.BRL.MIL>
Sender: netnews@ulysses.homer.nj.att.com
Reply-To: ekrell@hector.UUCP (Eduardo Krell)
Organization: AT&T Bell Laboratories
Lines: 20

In article <9089@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) ) writes:

>For example, sockets
>and streams are the two fundamental network connection technologies, and
>it is even possible that in SVR4 sockets are emulated via streams.

Well, to be more precise, sockets and streams are not at the same level
of abstraction. Streams are a general mechanism for implementing
a wide variety of communication protocols and IPCs. Sockets are a much
higher level abstraction and can be implemented in terms of (or on top of)
streams. This is how SVR4 will do it.

I don't know what you mean by sockets being "emulated via streams".
You can provide a socket library to present the same interface as
the socket related system calls in BSD. The point is that they don't
need be in the kernel anymore.
    
Eduardo Krell                   AT&T Bell Laboratories, Murray Hill, NJ

UUCP: {att,decvax,ucbvax}!ulysses!ekrell  Internet: ekrell@ulysses.att.com