public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Aurelio Medina <AMedina@xcaliber.com>
To: 'Phil Crescioli' <pcrescio@dsrnet.com>,
	pthreads-win32@sourceware.cygnus.com
Subject: RE: pthread, posix msg queues, and unix ipc
Date: Thu, 02 Aug 2001 13:00:00 -0000	[thread overview]
Message-ID: <1BDB01B13696D411BD6200D0B7C854EA01176901@chi-prd-mail1.xcaliber.com> (raw)

The main three differences why I choose POSIX IPC libraries over System V
IPC libraries are:
1) POSIX IPC is a portable standard.  Sys5 is not a portable standard.
2) POSIX IPC must be thread-safe.  Sys5 doesn't have to be and probably
isn't.
3) Although not neccesarily faster, POSIX IPC tends to be more up to date
and functional. 

I don't believe Linux has POSIX MQ yet however the files I sent can
certainly work on Linux.

Aurelio

-----Original Message-----
From: Phil Crescioli [ mailto:pcrescio@dsrnet.com ]
Sent: Thursday, August 02, 2001 1:33 PM
To: pthreads-win32@sourceware.cygnus.com
Subject: pthread, posix msg queues, and unix ipc


Hello all, 
I'm working on multiple platforms using pthreads and deciding on 
a message transfer mechanism for each platforms internal transfers
 - either posix message queues or unix IPC. 

Can someone tell me the main differences between Posix Message Queues and
Unix IPC message transfers using msgget(), msgsnd(), msgrcv() ?

Also, does Linux 2.x support posix message queues ?  I cant seem to find
mq_open, 
mq_send, etc.. on my Linux 2.4 box.  Is this a Linux add-on I need to
download off the net?

Thanks, 
Phil

             reply	other threads:[~2001-08-02 13:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02 13:00 Aurelio Medina [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-02 11:24 Phil Crescioli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1BDB01B13696D411BD6200D0B7C854EA01176901@chi-prd-mail1.xcaliber.com \
    --to=amedina@xcaliber.com \
    --cc=pcrescio@dsrnet.com \
    --cc=pthreads-win32@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).