On Wed, 2009-08-05 at 17:02 +0100, Chen, Congwu wrote:
I have a question maybe out of scope.
The "Connect" seems only covers Server Transport logic (can be
SyncML server or client), i.e. it's the peer contacting SyncEvolution.
What about Client Transport logic? GUI needs it to init EvolutionSyncClient
(can be both SyncML server or client). Will there be another method?
There are two solutions:
1. do it in-process, like we do at the moment for HTTP via
2. define a D-Bus interface for outgoing connections
Solution 1 might give better performance, but also creates additional
dependencies (and code) in our binary. The second solution might be
easier overall, but requires further discussion (how do we address the
peer which is to be contacted?) and changes in obexd.
We deferred that at the moment. Any ideas about the addressing issue?
The org.syncevolution.connection interface might be the same.
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.