linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ratheesh kannoth <ratheesh.ksz@gmail.com>
To: linux-c-programming@vger.kernel.org
Subject: message queue for two processes.
Date: Sat, 14 May 2011 21:10:11 +0530	[thread overview]
Message-ID: <BANLkTi=qk90bwxyG-_CKpqpfzz-Y5PMXMQ@mail.gmail.com> (raw)

There is a server (say A ) and two clients ( say  x and y ). These are
communicating thru message queue mechansim.  They are using same
message queue and different id to communicate.
i read like  -when a message is read , this will be removed from
message queue. Then, how can process x can read  only its intended
messages ?


-Ratheesh

             reply	other threads:[~2011-05-14 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-14 15:40 ratheesh kannoth [this message]
     [not found] ` <BANLkTimt9L4ZUS2--Cp7D5u+L6V6ZyjcbQ@mail.gmail.com>
2011-05-14 16:30   ` Fwd: message queue for two processes Aniruddha Bhattacharyya

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='BANLkTi=qk90bwxyG-_CKpqpfzz-Y5PMXMQ@mail.gmail.com' \
    --to=ratheesh.ksz@gmail.com \
    --cc=linux-c-programming@vger.kernel.org \
    /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 NNTP newsgroup(s).