Hi.
I'm working with QtServiceFramework for remote services on Linux. It
use QDbus as a backend and it's great.
But I find more convenient to use the QLocalSocket implementation for
development and debugging purposes since it's easier to deploy and
test - the service process has it output redirect
On quarta-feira, 2 de maio de 2012 13.59.02, Corentin Jabot wrote:
> The default value would be Native, corresponding on DBus where DBus is
> available.
>
> The library overhead should be minimal and this will not add
> additional dependency anywhere.
> It will also made easier the add of potential
ext Corentin Jabot wrote on 2012-05-02:
>
> bool
> QServiceManager::setInterProcessMethod(QService::InterProcessMethod);
>
> enum QService::InterProcessMethod {
>Native,
>LocalSocket,
>DBus
> }
>
Wouldn't
enum QService::InterProcessMethod {
Nativ
> From: "jan-arve.saet...@nokia.com"
>ext Corentin Jabot wrote on 2012-05-02:
>
>>
>> bool
>> QServiceManager::setInterProcessMethod(QService::InterProcessMethod);
>>
>> enum QService::InterProcessMethod {
>> Native,
>> LocalSocket,
>> DBus
>> }
>>
>Wouldn't
>
I made the change here https://codereview.qt-project.org/#change,25091
As suggested, I simplified the enum like that.
enum QService::InterProcessMethod {
Native,
LocalSocket,
}
The only thinks that changes are 2 new constructors
QServiceManager(QService::Scope scope, QServic
Original Message-
From: development-bounces+andrew.stanley-jones=nokia@qt-project.org
[mailto:development-bounces+andrew.stanley-jones=nokia@qt-project.org] On
Behalf Of ext Thiago Macieira
Sent: Wednesday, May 02, 2012 11:01 PM
To: development@qt-project.org
Subject: Re: [Developme
