I thought I\'d use Boost.Interprocess\'s Message Queue in place of sockets for communication within one host. But after digging into it, it seems that this library for some rea
I ran into a similar situation the other day when using Boost.Interprocess' sync classes: namely the condition class. It's implemented in a "generic" manner, but the way it has been done is to use a custom spinlock which is highly inefficient (on OS X at least). For all intents and purposes it made the sync classes useless.
In my experience the Interprocess library is pretty immature. I use it for shared memory, and it does work pretty well but there are some rough edges and I've had to hack around some "missing features" such as dynamically resizing shared memory etc.
In summary, don't expect this library to be a silver bullet just yet. It's good, but not exceptional at this time.