Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!munnari.oz.au!spool.mu.edu!caen!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!asuvax!noao!rstevens
From: rstevens@noao.edu (Rich Stevens)
Newsgroups: comp.unix.internals
Subject: Re: Quest: Sockets in SYSVR3
Message-ID: <1991Jun19.184132.29431@noao.edu>
Date: 19 Jun 91 18:41:32 GMT
References: <1991Jun17.190413.29256@sctc.com> <1991Jun18.130539.3579@sctc.com>
Distribution: comp.unix.internals
Organization: National Optical Astronomy Observatories, Tucson AZ
Lines: 19

> However, SYSVR4 does have sockets based on streams
> and I am curious how it maintains sockets for dup
> and fork operations.

For all the details on SVR4 sockets, take a look at

	%T Implementing Berkeley Sockets in System V Release 4
	%A I. Vessey
	%A G. Skinner
	%J Proceedings of the 1990 Winter USENIX Conference
	%C Washington, D.C.
	%P 177-193
	%D 1990

In summary, the paper says that it takes both a user library
(socklib) and a streams module (sockmod) to provide sockets
over streams.

	Rich Stevens  (rstevens@noao.edu)