[MeeGo-dev] Buteo / data synchronization in MeeGo: hello world!
corsac at debian.org
Thu Aug 19 04:44:39 PDT 2010
On 19/08/2010 13:33, sateesh.kavuri at nokia.com wrote:
>> I suppose Nokia didn't know about it when they started with Buteo.
>> Once this was discussed, it was too late to change direction under
>> the given constraints (staffing, time frame for the next release,
>> etc.). But this is becoming off-topic, let's focus on technical
>> questions here.
> [SK] Yes, that’s true. When Buteo was started, it is expected to be a
> Nokia only solution and none of the open source solutions satisfied
> our requirements (licensing also played some role here)
>>> In the wiki page, one can see:
>>>> * Device to device synchronization of PIM data (Contacts and
>> for now) based on SyncML
>>>> * Device to cloud synchronization of PIM data (ovi.com,
>> Scheduleworld.com etc.) based on SyncML
>>>> * Synchronization of media content to PC based on MTP * Device
>>>> to PC synchronization (currently only OviSuite, but this
>> requires contract with OviSuite to support a particular device)
>>> Why no “device to PC” using SyncML over bluetooth? It's quite
>>> convenient, especially since OviSuite isn't usable for a lot of
>>> people and since “device to device” seems already possible I
>>> guess it's just a special case with “device is a PC”.
> [SK] The device to PC solution could be implemented and is part of
> the MeeGo netbook roadmap. So, the idea is to synchronize MeeGo
> device data with a MeeGo netbook. The next step would be to support a
> Linux desktop sync solution. For Windows, there is already OviSuite
> and it does not make sense that create a new solution, given that it
> takes quite some effort to create a new Windows desktop sync
I'm not that interested in Windows anyway, to be honest. But there are
people out there using unix boxes and Mac OSX, too. Since the SyncML
standard exists and is already usable (though not in a really good shape
except for SyncEvolution maybe), what's important (imho) is to support
SyncML on the MeeGo devices as the “server” side (so desktop can request
sync from the device, using bluetooth for example).
>> But beware, the Wiki page describes the Buteo design, not the
>> current implementation or how it is used in a product. Right now,
>> device to MeeGo device synchronization is not possible with the
>> available code because there is no code which hooks up Buteo with
>> incoming OBEX/Bluetooth connections (feature request pending,
> [SK] Yes, there is already a request to implement this feature for
> MeeGo and hopefully we will bring it out by MeeGo 1.1 timeframe
It'd be really useful.
>>> (and I do hope that not just one calendar will be syncable, as
>>> it's the case on N900/Fremantle)
> [SK] The concept around multiple calendars in N900 (or anywhere) is
> that the end-user differentiates the various calendars (work,
> personal, google etc.) and would not want the data to be mixed up.
> For example, one would not want to mix the work events with the
> personal and expect them to endup in google server.
> So, choosing just 1 calendar to sync at a time is reasonable.
Emphasis on *at a time*. And by the way it's not possible to do that at
the moment to do that, everything as to be in the same calendar if you
ever want to sync it somewhere.
When using sync with the device as a “server” (meaning, another, non
MeeGo device, requests the sync), it should ask for which
calendar/contact/task/... it wants specifically.
When using sync with the device as the “client” (for another device or
to http servers or something) then when configuring that agreement on
the device, one would chose which calendar/contacts/tasks/.. to be part
of that agreement.
Not sure if I use “client”/“server” correctly, feel free to point me to
the correct terms.
More information about the MeeGo-dev