[MeeGo-dev] Buteo / data synchronization in MeeGo: hello world!

[Sateesh Kavuri]

On Saturday 21 August 2010 06:15 PM, ext Patrick Ohly wrote:
> On Sat, 2010-08-21 at 08:43 +0100, Sateesh Kavuri wrote:
>    
>>>>>> [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).
>>> It isn't clear to me how the URI the remote side specifies in the SyncML
>>> request interacts with the URI values in the service profiles (or, more
>>> importantly, the values in the user's own sync profiles).  Can you explain a
>>> bit more how the LocalURI and RemoteURI are used?
>>>
>>>        
>> The RemoteURI is used to identify a database on the remote service, so a
>> service XML would have this information whenever the device in question
>> would like to initiate sync with the target service. Similarly, a
>> LocalURI is published
>> to be used by other services when they would like to synchronize with
>> the host device
>>      
> So the LocalURI really only applies to SyncML, but not the local data,
> right?
>    
The LocalURI indicates the name (or id) of the local database that is used
> How is the local calendar selected? I assume this is in the user's sync
> profile.
The way the calendar is selected depends on the UI. For example the UI 
can have
an option to enable the user to select a Calendar from the list of 
available calendars, or
if it is a new target service (based on the target URL), a new calendar 
can be created
dynamically. Once a calendar is chosen based on the above, it would be 
added to the
profile.
> This is specific to the storage plugin referenced in the
> service profile. So a GUI which wants to configure that part of the sync
> profile needs to know which databases are supported by each storage
> plugin and which keys to set in the per-storage part of the sync
> profile.
>    
> It cannot get this information from Buteo at runtime, so in that sense a
> GUI is always written for a specific set of plugins which may appear in
> the service profiles, right?
>
>    
The engine can fetch this information for the GUI (like I mentioned 
above, there are few
options in which the Calendar can be created) and enable the user to 
choose a calendar.