Re: [Opensync-devel] SyncML plugin

[Quentin D. <que...@gm...>]

Well, it seems quite obvious for me that direct syncing between the phone and 
another group-member should be possible. That is why OBEX seems necessary to 
me, or how should I understand how libsynthesis is implemented in practice? A 
contact of mine, called Dinesh, has quite a good knowledge about this, 
especially since he wrote the syncml-plugin for syncevolution recently. He 
gave me the following answer which might interest you:

"Hey Quentin,

libsynthesis is just the syncml engine(comparing the data, updating the
right source etc...)... not the whole sync framework...SyncEvolution
 provides libsynthesis with the data sources, transport agents and a whole
other stuff...

Also, you might be interested to check this project called Buteo Sync(in
Meego's Website), which is the main synchronization framework for MeeGo...
and it replaced syncevolution for MeeGo..
currently it includes open source sync framework for:
1) Contacts
2) Calender
3) MPT (media transfer protocol: for music syncing)

and a closed source sync framework for:
1) SMS , MMS
2) Bookmarks etc..

Today i ve talked to the Nokia engineers behind this and they said it would
be totally open sourced really soon, once after they make it quite stable.

It
So you might want to look at this for the actual direction of
KMobileTools.(To enable KDE to )
Its a quite good and interesting project for us since:
1) it is Qt Based
2) maintained by Nokia and Intel!!!

If interested, i can let you know more about this :)

Cheers
Dinesh"

It seems that there is quite a potential solutions out there. All I want is a 
working SyncML for my mobile phone. ;-)

Kind regards,
Quentin


On Monday 13 December 2010 20:55:47 Emanoil Kotsev wrote:
> Thank you for your statement and for taking your time to put forward your
> standpoint.
> 
> > the SyncML plugin heavily depends on libsyncml. So I think
> > a rewrite and
> > the use of a different library would be a possible way. The
> > problem is
> > that libsynthesis does not provide OBEX support.
> 
> I read recently Nokia documentation that stated that not all OBEX features
> are supported by their implementation, so probably this is not an issue
> and perhaps it is better to get away from OBEX.
> 
> > I did stop my work because I cannot work on the plugin
> > during my work
> > time and I have some general concerns on the design of
> > SyncML and OpenSync.
> > 
> > SyncML merging will always be a problem. If a device is out
> > of sync and
> > there are changed items on both sides there is always the
> > risk of
> > duplicated entries. I can just note here that this
> > behaviour is just
> > unacceptable for customers with many contacts and events.
> > This leads to
> > our (university's) decision for Active Sync.
> > 
> > OpenSync introduces an additional problem for us. It syncs
> > all devices
> > at once and requires a slow sync if there was a problem
> > with just one
> > device. The following slow sync with an enabled merger can
> > create a
> > complexity which is simply too high. Just calculate the
> > effort for a
> > general merger and 5 devices with 100 items each.
> > 
> > So I personally prefer peer-to-peer and clear unique
> > identifier designs
> > for synchronization.
> > 
> > I hope somebody else has enough motivation to take over the
> > maintenance.
> > If you want to take over then you can expect that I am
> > willing to help
> > with informations.
> 
> I can just tell that these are complex decisions and I'm wondering who's
> going to take them.
> 
> If I'm understanding you right you suggest that because of the slow sync it
> is better to sync in pairs separately the desired types. In fact this was
> the safe part of my testing. Contats - Contacts
> Calendar - Calendar
> etc
> 
> About the syncml plugin it might be easier to write a libsynthesis based
> plugin from scratch.
> 
> But in the current situation I have just a minor problem with an entity not
> being accepted by the parser as I documented in the bug. It might be
> easier to fix this one instead of discussing and doing some unnecessary
> work.
> 
> Very sad, that you don't have the time and the motivation to work on it,
> but you have my complete understanding about it.
> 
> It would be nice if you can organize a hand over in some form - upload to
> svn or whatever
> 
> Thanks for the work so far
> 
> Some questions:
> 
>  If I have write access to svn, can I update syncml code or do I need extra
> permitions for it?
> 
>  Is there a way to emulate connected phone, because it is cumbersome when
> testing.
> 
>  Documentation - also links and docs that you've used?
> 
> regards
> 
> 
> 
> 
> ---------------------------------------------------------------------------
> --- Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d
> _______________________________________________
> Opensync-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-devel