Re: [SyncEvolution] D-Bus API: session ID
On Wed, 2009-09-23 at 02:23 +0100, Zhao, Forrest wrote:
Ohly, Patrick wrote:
> 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?
Since obexd does not use sesssion ID in the D-Bus API (i.e. it's
ignored by obexd), such kind of change does not matter much to obexd.
I made the change, please update your code to match the new signature. I
didn't change the comments, because it was already worded such that
ignoring the the session ID was valid ("The caller is responsible for
ensuring that only messages belonging to this session are passed to
future process() calls." - this automatically the case with OBEX).
--
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.