# Ruby IPC: messaging, blackboard, etc.? **URL:** \ **Category:** Ruby\ **Created:** [September 24, 2006, 12:03pm UTC](https://www.ruby-forum.com/t/ruby-ipc-messaging-blackboard-etc/69816 "2006-09-24T12:03:51Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![dokondr](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/3be4f8/32.png) [@dokondr](https://www.ruby-forum.com/u/dokondr)\ **Post date:** [September 24, 2006, 12:03pm UTC](https://www.ruby-forum.com/t/ruby-ipc-messaging-blackboard-etc/69816/1 "2006-09-24T12:03:51Z")
I am looking for Ruby crossplatform local and network IPC: messaging, blackboard, etc. It would be great to find a survey of existing projects in this area. Things I am most interested in: 1. Distributed blackboard or any other publish/subscribe mechanism that scales well with new nodes comming into play 2. Messaging system that will allow address messages to removed\_email\_address@domain.invalid Thanks! Dima ---
**Author:** ![dokondr](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/3be4f8/32.png) [@dokondr](https://www.ruby-forum.com/u/dokondr)\ **Post date:** [September 24, 2006, 7:34pm UTC](https://www.ruby-forum.com/t/ruby-ipc-messaging-blackboard-etc/69816/2 "2006-09-24T19:34:12Z")
On Sun, Sep 24, 2006 at 07:03:53PM +0900, Dmitri K. wrote: > Dima I think your first step would be to look into drb (distributed ruby) which comes with ruby. ---
**Author:** ![dokondr](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/3be4f8/32.png) [@dokondr](https://www.ruby-forum.com/u/dokondr)\ **Post date:** [September 24, 2006, 7:54pm UTC](https://www.ruby-forum.com/t/ruby-ipc-messaging-blackboard-etc/69816/3 "2006-09-24T19:54:15Z")
On Sep 24, 2006, at 12:32 PM, Logan C. wrote: > > removed\_email\_address@domain.invalid > > > > Thanks! > > Dima > > I think your first step would be to look into drb (distributed ruby) > which comes with ruby. #1 is a request for Rinda’s Tuplespace built on DRb and also comes with Ruby. The Ruby Cookbook shows example usage for this. I didn’t understand #2. James Edward G. II ---
**Author:** ![dokondr](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/3be4f8/32.png) [@dokondr](https://www.ruby-forum.com/u/dokondr)\ **Post date:** [September 24, 2006, 8:02pm UTC](https://www.ruby-forum.com/t/ruby-ipc-messaging-blackboard-etc/69816/4 "2006-09-24T20:02:15Z")
On 9/24/06, Dmitri K. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > I am looking for Ruby crossplatform local and network IPC: messaging, > blackboard, etc. It would be great to find a survey of existing projects > in this area. > Things I am most interested in: > > 1. Distributed blackboard or any other publish/subscribe mechanism that > scales well with new nodes comming into play > 2. Messaging system that will allow address messages to > removed\_email\_address@domain.invalid I don’t quite understand #2 but you can look at reliable-msg, which is a very fine piece of work by Assaf Arkin. In addition, I’ve been working on a full-featured message-queueing system that should be ready for an early look quite soon. ---
**Author:** ![dokondr](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/3be4f8/32.png) [@dokondr](https://www.ruby-forum.com/u/dokondr)\ **Post date:** [September 24, 2006, 11:10pm UTC](https://www.ruby-forum.com/t/ruby-ipc-messaging-blackboard-etc/69816/5 "2006-09-24T23:10:47Z")
Francis C. wrote: > On 9/24/06, Dmitri K. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > > I am looking for Ruby crossplatform local and network IPC: messaging, > > blackboard, etc. It would be great to find a survey of existing projects > > in this area. > > Things I am most interested in: > > > > 1. Distributed blackboard or any other publish/subscribe mechanism that > > scales well with new nodes comming into play > > 2. Messaging system that will allow address messages to > > removed\_email\_address@domain.invalid > > I don’t quite understand #2 but you can look at reliable-msg, which is a > very fine piece of work by Assaf Arkin. In addition, I’ve been working > on a > full-featured message-queueing system that should be ready for an early > look > quite soon. By 2) I mean a messaging framework where addressable unit is a thread. In other words, in such a system a following scenario would be possible: Thread\_X @ Process\_A @ Host\_N \<— snd/rcv messages —\> Thread\_Y @ Process\_B @ Host\_M (Framework may provide peer registration and naming mechanisms (for all parts of such address). For example, process name or PID used in native OS and network host name (IP addr) may be quite naturally used. As for threads, there may be an agreement on how their names are built (such as natural numbers, logical names, etc.)) Dima