On Friday 20 August 2010 13:39:34 Patrick Ohly wrote: > On Fri, 2010-08-20 at 11:41 +0100, Graham Cobb wrote: > > On Friday 20 August 2010 07:54:00 Patrick Ohly wrote: > > [...] > > > And it is working because we seem to have uncovered two design bugs > > already. One already reported and the other not. > > Which one wasn't reported?
The scheduler. See http://bugs.meego.com/show_bug.cgi?id=5619. I am not saying it was necessarily the wrong decision when it was merged, but that doesn't stop it needing to be fixed as soon as a system scheduler is available. > > > [multiple calendars] > > > > > > > > [SK] This agreement is something that would be part of the protocol > > > > > in use. Apparently SyncML does not have this facility. > > > > > > It does. uri=calendar/work and uri=calendar/personal can be used. The > > > only problem is that most existing services do not offer that. > > > > In my limited experience, most services seem to allow the URI to be > > specified (not least because of the different values expected by > > different devices). > > Sync client allow it to be specified because it typically varies among > services, as you said, but which service let's you configure multiple > URIs? SyncEvolution and your custom Synthesis allow that, but I'm not > aware of a consumer service supporting that. In the sense that one can set up different accounts which sync the same device but specify different URIs. By the way, the various bug reports make mention of required use cases. Can these requirements be published somewhere so we can all read them? Graham _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
