On Mon, 2009-09-14 at 22:46 +0200, Patrick Ohly wrote: > On Wed, 2009-09-09 at 23:25 +0200, Patrick Ohly wrote: > > I'll continue to work on the sync-related methods. Because this is in a > > different part of the file, we should be able to merge changes easily. > > Hurray! It syncs! Spending some time on a plane or train away from new > email is a very productive way to move ahead with implementation > work ;-) > > The code on the "dbus-api" branch now implements running a sync session.
Now it also supports that via the Connection API, albeit without proper support for Server Alerted Notifications, which are necessary for Bluetooth. Using the SanPackage class from the Synthesis source code should be fairly straightforward, except that picking a configuration will be difficult inside the current configuration scheme. My goal is to make it work with a fixed "bluetooth" configuration (so that Forrest can test his code) and then properly solve the issue with rearranging the configuration layout, as discussed before. Forrest, how are we doing with regards to the schedule? Do you have enough to get started right now? When do you need full SyncML client support via OBEX implemented? -- 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 [email protected] http://lists.syncevolution.org/listinfo/syncevolution
