Network based messaging

Josh Coates jcoates at
Sat Jul 26 09:08:16 MDT 2008

why not just write your own using the original awesomeness that is berkeley
sockets? steven's latest revision:  (source code
gzip'd and online)

or just cut & paste the basics from wikipedia:

a little more work, a little more control, and a lot more fun.  ;-)


On Thu, Jul 24, 2008 at 4:36 PM, Dave Smith <dave at> wrote:

> I've been looking for a good messaging system in Linux to send simple
> messages between different pieces of software I'm developing. I would like a
> central messaging service that handles moving messages around the network
> for me, such that each application can connect to the messaging service and
> get messages as they arrive. The messages are of a broadcast nature and each
> app doesn't necessarily need to know about all the other apps who happen to
> care about its messages (they should remain de-coupled). The various
> applications will not be on the same host, so network-based is a must, and
> it must be able to span broadcast domains.
> I've looked at JMS and threw it out because of the Java dependencies. My
> software is mostly Python and C++. I also looked at (and used) CORBA, but
> it's too complex and the learning curve is killer. What I really want is
> D-Bus, but currently D-Bus doesn't support remote messaging[1] since it
> relies on Unix Domain Sockets.
> Any ideas?
> --Dave
> [1] The D-Bus guys working on it:
> /*
> PLUG:, #utah on
> Unsubscribe:
> Don't fear the penguin.
> */

More information about the PLUG mailing list