Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!mips!sgi!rpw3@rigden.wpd.sgi.com
From: rpw3@rigden.wpd.sgi.com (Rob Warnock)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: What is a UNIX Domain Socket?
Keywords: UNIX DOMAIN SOCKET
Message-ID: <70577@sgi.sgi.com>
Date: 28 Sep 90 06:44:07 GMT
References: <82@unigold.UUCP> <1990Sep27.180632.25841@dg-rtp.dg.com>
Sender: guest@sgi.sgi.com
Reply-To: rpw3@sgi.com (Rob Warnock)
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 25

In article <1990Sep27.180632.25841@dg-rtp.dg.com> harvey@dg-rtp.dg.com
(Michael Harvey) writes:
+---------------
| Sockets support two communications domains: the UNIX domain
| for process-to-process communication on the same host,
| and the Internet domain for process-to-process communication
| between hosts that communicate with one another using the
| DARPA standard communication protocols, such as IP, TCP, and UDP.
+---------------

The [Berkeley] socket model supports an arbitrary number of domains.
Let's not forget the XNS domain (Xerox NS), which uses Xerox standard
protocols (ITP, Courier, Clearinghouse), or the XTP domain (Protocol
Engines Inc.'s protocol), or VMTP, or whatever...

...even if AF_INET *is* the most common.


-Rob

-----
Rob Warnock, MS-9U/510		rpw3@sgi.com		rpw3@pei.com
Silicon Graphics, Inc.		(415)335-1673		Protocol Engines, Inc.
2011 N. Shoreline Blvd.
Mountain View, CA  94039-7311