home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.wizards:3887 comp.unix.programmer:4630 comp.unix.internals:1794
- Path: sparky!uunet!mcsun!uknet!gdt!aber!aberfa!pcg
- From: pcg@aber.ac.uk (Piercarlo Grandi)
- Newsgroups: comp.unix.wizards,comp.unix.programmer,comp.unix.internals
- Subject: Re: Implementation of Sys V. based message queues
- Message-ID: <PCG.92Sep10184015@aberdb.aber.ac.uk>
- Date: 10 Sep 92 18:40:15 GMT
- References: <32301@adm.brl.mil> <1992Sep1.155322.5522@panther.mot.com>
- <acourtny.715558246@unix1.tcd.ie>
- Sender: news@aber.ac.uk (USENET news service)
- Reply-To: pcg@aber.ac.uk (Piercarlo Grandi)
- Organization: Prifysgol Cymru, Aberystwyth
- Lines: 21
- In-Reply-To: acourtny@unix1.tcd.ie's message of 3 Sep 92 22: 10:46 GMT
- Nntp-Posting-Host: aberdb
-
- On 3 Sep 92 22:10:46 GMT, acourtny@unix1.tcd.ie (Antony A. Courtney) said:
-
- acourtny> All the system V IPC mechanisms are completely inconsistent
- acourtny> with the rest of the i/o facilities provided by Unix.
-
- And for a damn good reason! They do not come from Unix, really. The
- reason for which they exist at all, when named pipes would have been
- sufficient, is that a particular group within AT&T used a particular
- version of something that looked like Unix, and they needed for their
- real time application (switching) an especially fast, if crude, IPC
- mechanism, so they came up with a set of interfaces that were custom
- designed for their application and nothing else.
-
- Then they lobbied hard the internal AT&T Unix Support Group so that the
- specs for their custom IPC were added to the standard interfaces so they
- did not have to port their implementation to each new release of Unix,
- but USG did it for them.
- --
- Piercarlo Grandi | JNET: pcg@uk.ac.aber
- Dept of CS, University of Wales | UUCP: ...!aber-cs!pcg
- Penglais, Aberystwyth SY23 3BZ, UK | INET: pcg@aber.ac.uk
-