Andy, have you seen the question below? Does the libeassync depend on non-empty client IDs?
Bye, Patrick On Sun, 2011-06-19 at 15:17 +0200, Patrick Ohly wrote: > Hello all! > > I have implemented an ActiveSync backend for the ActiveSync > implementation developed by Mobica. Code is currently in the activesyncd > git repo. It is hosted there because the activesyncd library API is not > stable yet. Long term it'll probably move back to SyncEvolution. > > I only tried compilation inside SyncEvolution. I haven't even tried to > run it at this point. I'll try to find the time for that tomorrow. > > See the README for more instructions: > http://git.infradead.org/activesyncd.git/blob/HEAD:/syncevolution/README > > The backend itself already supports all four data categories, but only > calendar events are supported by the EAS library at this time. > > There's also quite a bit of work left. The EAS library doesn't allow > distinguishing between different error scenarios, so right now > everything, including temporary network errors, forces a slow sync in > the next sync session. > > I went for the simplest possible approach. Batching multiple changes to > the server side into one final call would be useful. It's easy enough > for deletes, but a bit harder for adds, because the Synthesis engine > needs to know the final ID. This can be solved by assigning a temporary > ID and reporting the final one later. > > Question to Mobica: right now, the client_id is not set at all by the > SyncEvolution backend. Will your code handle that? > _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
