Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!rutgers!apple!bionet!ames!sgi!calcite!vjs
From: vjs@calcite.UUCP (Vernon Schryver)
Newsgroups: comp.unix.sysv386
Subject: Re: Sockets in 386/ix
Summary: named pipes
Keywords: sockets, ix, 386
Message-ID: <95@calcite.UUCP>
Date: 29 Sep 90 17:14:10 GMT
References: <6168@uceng.UC.EDU>
Organization: Rhyolite Software, Mountain View, CA
Lines: 18

In article <6168@uceng.UC.EDU>, sramacha@uceng.UC.EDU (Sridhar Ramachandran) writes:
> I need Unix domain sockets to create a communication channel between
> two processes.

My day-time employer (a major UNIX workstation vendor) has been shipping
SVR3 with 4.3BSD TCP/IP for about four years.  For the first three years,
we did not implement "UNIX domain sockets," because we value speed and
dislike the loss of user physical memory and consequent slowness caused by
modern, bloated kernels.  Instead, we told customers to use System V "named
pipes."  We finally added UDS sockets as an optional lboot module as a
result of some internal political baloney.  There was and is limited end
user need or demand for them.

Aside from details likes select(2) (which may be fixed by your vendor--I
don't know), SVR3 named pipes are very similar to UNIX domain sockets.


Vernon Schryver,    vjs@calcite.uucp