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

[David Boosalis]

QLocal Socket would fit the bill rather nicely I think.  On Linux it is
going to be implemented with shared memory and on Windows QLocalSocket uses
pipes.  There is a convenient class called QLocalServer. I 've used
LocalSockets for this kind of commutation on a headless server machine
running Ubuntu Server.  If your main event thread is doing other things
related to boost or your own C++ code, then you will probable want to run
the QLocalServer in its own QThread and do an exec() call so it will have
its own event loop.



On Wed, Dec 22, 2010 at 7:44 AM, Ed Sutton <ESutton at fescorp.com> 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.
>
> -Ed
>
> _______________________________________________
> Qt-interest mailing list
> Qt-interest at qt.nokia.com
> http://lists.qt.nokia.com/mailman/listinfo/qt-interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20101223/20ca64d5/attachment.html