Closed chriadam closed 9 years ago
@blammit @VDVsx @pvuorela
Note: the other possibility is that we could modify the generated client profile for the bt device, by updating the UUID field to point to the actual local device calendar uid instead of the randomly generated one.
However, I'm not certain how to do something similar for the server syncml plugin... That is, which notebook would be used when we are the server rather than initiator of the sync...
This commit enables calendar sync over Bluetooth. In order to do so, it does several things:
1) adds the hcalendar storage backend as a supported storage backend for the syncml server plugin
2) modifies the calendar backend to access the appropriate local device notebook
3) modifies the calendar storage plugin so that it now ignores the (randomly generated) KEY_UUID value when requesting access to the calendar backend.
Contributes to MER#1222