From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: "Maksim (Max) Krasnyanskiy" <maxk@qualcomm.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
jt@hpl.hp.com,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Question : Broadcast Inter Process Communication ?
Date: Tue, 21 May 2002 10:00:06 +0200 [thread overview]
Message-ID: <3CE9FE86.3060808@loewe-komp.de> (raw)
In-Reply-To: <20020517195438.A30640@bougret.hpl.hp.com> <5.1.0.14.2.20020520094738.068778a0@mail1.qualcomm.com>
Maksim (Max) Krasnyanskiy wrote:
>
>> > That's exactly why I don't want to deal with it myself.
>> > However, the kernel deal with it all the time, and do it
>> > well. For example RtNetlink event have this property (except that they
>> > are kernel => process instead of beeing process => process).
>>
>> By sending one copy of the message to each target. Its how everyone does
>> it except for special cases. Reliable multi-delivery is -hard-
>
>
> I was gonna suggest the same thing. Why not just have a simple event
> server based on unix sockets.
> This server would listen on unix stream socket. Clients interested in
> events would connect to it.
> All the server has to do is copy event to all connected clients.
> Server code is very simple. About 20 lines, everything in a single
> thread, if you use GLib's event loop.
>
If using a central "server" process, all clients have to copy
the message to the server - then the server copies the messages
to multiple clients.
I can imagine a library, that holds a registry in shared mem, and
the clients look for themselves to whom to copy the message.
For this I want to use posix message queues to avoid lots of
context switches and copies.
prev parent reply other threads:[~2002-05-21 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 21:30 Question : Broadcast Inter Process Communication ? Jean Tourrilhes
2002-05-18 1:52 ` Olaf Dietsche
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 [this message]
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=3CE9FE86.3060808@loewe-komp.de \
--to=pwaechtler@loewe-komp.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.