mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Olaf Dietsche <olaf.dietsche--list.linux-kernel@exmail.de>
To: jt@hpl.hp.com
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Question : Broadcast Inter Process Communication ?
Date: Sat, 18 May 2002 03:52:33 +0200	[thread overview]
Message-ID: <873cwqrzmm.fsf@goat.bogus.local> (raw)
In-Reply-To: <20020517143052.A30047@bougret.hpl.hp.com>

Hi Jean,

Jean Tourrilhes <jt@bougret.hpl.hp.com> writes:

> 	I was looking under Linux for a mechanism to distribute an
> event from one process (a daemon) to a set of other processes (deamons
> or applications). The number and indentity of those other processes
> would not be known by the process generating the event, those
> processes would register themselves dynamically to the stream of
> event. And the event need to be delivered to all of them (not only the
> first one).
> 	In other words, it would look like a *broadcast* message
> queue, where the sender process would create the queue and write
> events to it, and the other bunch of processes would dynamically open
> the queue and listen for events.

[snip]

> 	This "one sender - multiple reader" model seems common and
> usefull enough that there must be a way to do that under Linux. I know
> that it exist under Windows. Can somebody help me to find out how to
> do it under Linux ?


Maybe, you're looking for multicast. But you need a TCP/IP stack for
this and I don't know, wether this is implemented in Linux.

Regards, Olaf.

  reply	other threads:[~2002-05-18  1:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-17 21:30 Jean Tourrilhes
2002-05-18  1:52 ` Olaf Dietsche [this message]
2002-05-18  1:57   ` Jean Tourrilhes
2002-05-18  3:04 ` Alan Cox
2002-05-18  2:54   ` Jean Tourrilhes
2002-05-18  3:23     ` Alan Cox
2002-05-20 17:03       ` Maksim (Max) Krasnyanskiy
2002-05-21  8:00         ` Peter Wächtler

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=873cwqrzmm.fsf@goat.bogus.local \
    --to=olaf.dietsche--list.linux-kernel@exmail.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®