Hi Patrick,
To get started quickly, a new backend could derive from the TrackingSyncSource and simply not implement any kind of change tracking and writing. In terms of the TrackingSyncSource API that means that the derived class provide a list of IDs without revision strings and only implements the item read method.
Thanks for the info. I'm going to do some tests following your suggestion, but I already have some questions:
1. Assuming this backend needs to have D-Bus communication to another daemon (obex-client), how would it access the mainloop in order to have pseudo-blocking calls?
2. For the non-supported backend functionality (particularly write operations), what would be the proper thing to do? Just omit the calls?
Cheers, Mikel _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
