[Development] Dynamic QtServiceFramework backend.

BRM bm_witness at yahoo.com
Thu May 3 02:01:48 CEST 2012

> From: "jan-arve.saether at nokia.com" <jan-arve.saether at nokia.com>

>ext Corentin Jabot wrote on 2012-05-02:
>> bool
>> QServiceManager::setInterProcessMethod(QService::InterProcessMethod);
>> enum QService::InterProcessMethod {
>>            Native,
>>            LocalSocket,
>>            DBus
>> }
>enum QService::InterProcessMethod {
>           Native,
>           LocalSocket
>be sufficient?
>I've hardly used the service framework, but I don't see why DBus enum value is strictly needed, since it would lead to less portable code:
>is less portable than
>Limiting the enum values to be cross-platform would keep the API simpler, and _maybe_
>the implementation would be simpler too, since we don't have to deal with the condition
>where the desired IPC mechanism is not available. 

What about platforms where the developer wants to use D-bus but it is _not_ the native IPC? (e.g. Windows)
That said, how would this account for configuring D-Bus for local or network sockets?



More information about the Development mailing list