I see 'syncevo-connection-full.xml' in the dbus api interfaces directory. It is
used to pass messages, such OBEXD, right?
Have all the interfaces already been defined in the file?
[mailto:email@example.com] On Behalf Of Patrick Ohly
Sent: Tuesday, September 22, 2009 5:30 PM
To: Zhao, Forrest
Subject: [SyncEvolution] D-Bus API: session ID
The main reason for making the session ID in the D-Bus API an uint32_t
was that this might have allowed obexd to map this to the OBEX
connection ID. As we discussed, this doesn't work.
Therefore I think we can change that part of the API. I'd like to turn
uint32_t into a string, to make the range of valid session IDs broader
(required if Synthesis server chooses it).
In practice, the session ID will only be used to re-establish a
connection, in other words, in the initial Process() call. This isn't
part of the API contract at the moment. Should we document it and thus
allow obexd to completely ignore the session ID?
I can make the change now, but don't want to ruin the first round of
testing between obexd and SyncEvolution without giving advance
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.
SyncEvolution mailing list