From: "Craig A. Vanderborgh" <craigv@voxware.com>
To: pthreads-win32@sources.redhat.com
Subject: Shared mutexes & condvars
Date: Thu, 27 Mar 2003 20:54:00 -0000 [thread overview]
Message-ID: <1048798679.32756.49.camel@zetar> (raw)
Hello all:
I am interested in getting shared (between processes..) mutexes and
condvars to work for pthreads-win32. The application we need them for
is an interprocess version of Aurelio Medina's POSIX message queue. His
code presumes that support for process-shared synchronization objects
exists in pthreads-win32. Which it does not at the moment.
I am back-porting his code to the raw WIN32 synchronization calls and
I'm sure I can get this to work on WINCE, but I hate to do this because
it really seems like we're going in the wrong direction. I'd be willing
to help make mutex/condvar process-shared if I can. Does anyone else
have any interest in getting this done?
regards,
craig vanderborgh
voxware incorporated
reply other threads:[~2003-03-27 20:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1048798679.32756.49.camel@zetar \
--to=craigv@voxware.com \
--cc=pthreads-win32@sources.redhat.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).