Sean Boudreau(deleted)
|
Re: Local (Unix domain) socket performance on QNX
|
Sean Boudreau(deleted)
11/07/2008 12:45 PM
post16232
|
Re: Local (Unix domain) socket performance on QNX
On Tue, Nov 04, 2008 at 01:53:31PM -0500, Glenn Schmottlach wrote:
> Would there be any advantage (from a performance perspective) of using the mq server to implement an asynchronous
messaging facility instead of local domain sockets? Inherently, DBUS is a messaging protocol that supports (typically)
two message buses - the system and session buses. These "buses" appear as mount points in the Linux file system and are
typically specified in an environment variable so programs can find them. Ideally, I'd like to use an analogous
mechanism in QNX that appears as a path in the file system. It seems that the mq server might offer this facility in a
more efficient manner than the local domain socket approach. Is it possible for more than one process to send/receive to
a mq or is a single producer/consumer model expected? I guess with local sockets a server (the bus daemon) can listen
and handle multiple connections. I wasn't sure if the mq provides a similar facility.
You can have multiple senders / receivers on a message queue.
Personally I'd do whatever is easiest since this whole dbus
thing seems a lot like the qnx message bus: attaching to the
namespace to receive messages. The 'correct' port may be to
look at resmgr_attach() and native messaging which mqueue and
AF_LOCAL are based on.
-seanb
|
|
|