# Re: local interprocess communication ideas

**URL:** <https://www.ruby-forum.com/t/re-local-interprocess-communication-ideas/82257>\
**Category:** Ruby\
**Created:** [January 18, 2007, 4:05pm UTC](https://www.ruby-forum.com/t/re-local-interprocess-communication-ideas/82257 "2007-01-18T16:05:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![piet](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/a9adbd/32.png) [@piet](https://www.ruby-forum.com/u/piet)\
**Post date:** [January 18, 2007, 4:05pm UTC](https://www.ruby-forum.com/t/re-local-interprocess-communication-ideas/82257/1 "2007-01-18T16:05:19Z")

</div>

> -----Original Message-----  
> From: James Mills [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)]  
> Sent: woensdag 17 januari 2007 23:31  
> To: ruby-talk ML  
> Subject: local interprocess communication ideas.
> 
> So, with all of that info, what does the community recommend  
> for a lightening fast interprocess communication method?

Not sure what your platform is, but check  
[http://rubyforge.org/projects/sysvipc/](http://rubyforge.org/projects/sysvipc/) (when it’s back up)  
I’ve used this to accept messages generated by a C++ process. Works like  
a charm and is very fast.

Piet.
