home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.wizards:3842 comp.unix.programmer:4567 comp.unix.internals:1775
- Newsgroups: comp.unix.wizards,comp.unix.programmer,comp.unix.internals
- Path: sparky!uunet!ddssuprs!lpc
- From: lpc@dickens.com (Luis P Caamano)
- Subject: Re: Implementation of Sys V. based message queues
- Message-ID: <1992Sep8.171014.21414@dickens.com>
- Date: Tue, 8 Sep 1992 17:10:14 GMT
- References: <1992Sep1.155322.5522@panther.mot.com> <acourtny.715558246@unix1.tcd.ie> <1992Sep3.232807.18181@noao.edu>
- Organization: Dickens Data Systems, Inc.
- Lines: 28
-
- In article <1992Sep3.232807.18181@noao.edu> rstevens@noao.edu (W. Richard Stevens) writes:
- >>> I would like to be able to use select(2) to multiplex descriptor based
- >>> objects (sockets) as well as the message queue.
- >>
- >> I could be mistaken, but my experience with using Sys V IPC with select()
- >> is: 'aint no way...
- >
- >Believe it or not, I just found out that AIX on the RS/6000 actually
- >provides a function named select() with a different interface that
- >actually lets you multiplex both descriptors and message queues.
- >When I saw their interface I almost barfed.
-
- Why? Is the implementation so awful? I remember I almost barfed too but
- just because it was a new, strange select() that wasn't what I was used
- to see.
-
- Anyway, I'm not trying to say that it's a great implementation, that
- I don't know now, I just want to hear why it's bad.
-
- At least they did something ...
- --
- ---------------------------------------------------------------------------
- Luis P. Caamano | lpc@dickens.com
- Dickens Data Systems, Inc. | uunet!dickens.com!lpc
- Atlanta, GA | (404) 475-8860
- ---------------------------------------------------------------------------
- If I think I know it all, I'll stop learning. -myself
- The more I learn, the more I know I know nothing. -somebody else
-