[Qt-interest] Linux Interprocess communication for GUI to connect to a service ?

[Arnold Krille]

On Wednesday 22 December 2010 16:44:35 Ed Sutton wrote:
> Is QtDBus the best choice?
> 
> My application is a gigabit packet analyzer tool.  I started out with an
> API that communicates with the Qt GUI using boost signals and slots.  The
> analyzer sends periodic status updates and event signals to the GUI for
> various packet error conditions.  The API and GUI run in the same process.
>  I wish to evolve this to a headless daemon service and allow a GUI to be
> launched that communicates and displays status of the packet analyzer
> tool.
> 
> Any feedback on experience with Linux interprocess communications and
> especially performance aspects are appreciated.

If you want your service to be fully headless-capable, this will probably also 
mean network-transparent. If yes, this rules out dbus, shared memory and local 
sockets.

Yes, dbus is meant to be network-transparent. But thanks to the security 
implementation, the only way of getting the authentication right is when used 
on the same computer. Pretty useless for networks. I developed my own text-
based protocol to run via qtcpsocket.

Maybe that helps in your decision.

Have fun,

Arnold
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20101222/dc7f396c/attachment.bin