Subj : IPC message-queues: msgrcv() vs pipes/sockets? ACE?
To   : comp.programming.threads
From : Matt
Date : Sat Jul 23 2005 12:10 am

I want to implement a complex, multi-process (and multiple threads per
process) network server system. I suspect that socket- or pipe-based
inter-process communication (IPC) will incur too much overhead.

Will the following message-queuing mechanisms (via the msg*()
functions) support the same capability (as sockets or pipes) with less
overhead (ie, make the overall system go faster)? 

http://www.opengroup.org/onlinepubs/007908799/xsh/ipc.html

Any other suggestions/alternatives?

Free/open-source alternatives work best.  I also prefer a
cross-platform solution between Linux and BSD solutions, possibly
Windows as well (but we can live without Windows support).

My software development team is also trying to get a similar mechanism
to work with ACE ( http://www.cs.wustl.edu/~schmidt/ACE.html ), and
while ACE's thread-pool management seems to work ok, we do not as of
yet see a means to manage shared-memory message queues in ACE in order
to support communication across completely-separate
processes/applications that do not share the same thread hierarchy.
Another developer on my team is posting more question details on this
topic at comp.soft-sys.ace.

Thanks for any help,
-Matt
--
Remove the "downwithspammers-" text to email me.

.