From: "Scott McCaskill" <scott@magruder.org>
To: <pthreads-win32@sourceware.cygnus.com>
Subject: Re: posix msg queues
Date: Tue, 07 Aug 2001 09:00:00 -0000 [thread overview]
Message-ID: <006401c11f5a$1bed0380$3e0f020a@hand.local> (raw)
In-Reply-To: <MEEGJNAGDGABKCMJEPIHIEKKCAAA.rotem.shacham@bluesoft-inc.com>
try doing a search for "posix message queue" on google
----- Original Message -----
From: "Rotem Shacham" <rotem.shacham@bluesoft-inc.com>
To: "Posix Mailing list" <pthreads-win32@sourceware.cygnus.com>
Sent: Tuesday, August 07, 2001 11:17 AM
Subject: RE: posix msg queues
> Hi,
> Can you please give me a lead as to were can I find some info on Posix MQ
?
>
> 10x
> Rotem.
>
> -----Original Message-----
> From: pthreads-win32-owner@sources.redhat.com
> [ mailto:pthreads-win32-owner@sources.redhat.com]On Behalf Of Aurelio
Medina
> Sent: Tuesday, August 07, 2001 4:27 PM
> To: 'Phil Crescioli'
> Cc: 'pthreads-win32@sourceware.cygnus.com'
> Subject: RE: posix msg queues
>
>
> Phil,
>
> As Ross J. pointed out earlier the PTHREAD_PROCESS_SHARED attribute is not
> yet available. What this means for the POSIX MQ code that I provided is
> that it is not safe to use on Win32 if you have more than one process
using
> the same MQ. It is still safe on other systems that support this
attribute
> but do not have a MQ library available.
>
> NOTE: I use POSIX MQ in my Win32 apps to queue data between two threads in
> the same process. It is safe to use in this fashion. Hopefully the
> PTHREAD_PROCESS_SHARED attribute will become available later.
>
> Aurelio
>
> -----Original Message-----
> From: Phil Crescioli [ mailto:pcrescio@dsrnet.com ]
> Sent: Tuesday, August 07, 2001 7:19 AM
> To: Aurelio Medina
> Cc: 'pthreads-win32@sourceware.cygnus.com'
> Subject: posix msg queues
>
>
> Aurelio,
>
> Got your posix tester code working on solaris2.7, hpux11.0, and windoze
> 2000.
> Thanks for making the posix port to win32 painless! Actually I modified
the
> tester.c
> code to send a data structure with the message buffer as one of the fields
> in the
> structure, as my project requires, and every msg receive I go through a
> sequence
> checking algorithm to make sure I dont drop data, etc...
>
> I'm now breaking this modified tester.c into two processes where one is a
> sender
> and the other a receiver. All compiles and runs, but the receiver never
> gets the data.
> Im looking at mq_open on Solaris and trying to undertsand what might be
the
> reason
> why the reciever process never gets the data from the sender process?
>
> Any ideas? Know of any tutorials on posix ipc out?
>
> Thanks,
> Phil
>
>
> =======================================
> =======================================
> Phil Crescioli
> Software Engineer
> Digital System Resources Innovative solutions
> (o)703-263-7405 for today's systems
> (c)703-408-5198 and tomorrows
> pcrescioli@dsrnet.com applications..
> http://www.dsrnet.com
> =======================================
> Resume
> http://users.erols.com/madisons/resume/resume.html
> =======================================
>
>
next prev parent reply other threads:[~2001-08-07 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-07 8:20 Rotem Shacham
2001-08-07 9:00 ` Scott McCaskill [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-07 7:26 Aurelio Medina
2001-08-07 5:11 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='006401c11f5a$1bed0380$3e0f020a@hand.local' \
--to=scott@magruder.org \
--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).