On Sun, 2012-06-03 at 02:01 +1200, Jane Atkinson wrote:
> In any case, in the past I've used the Start from Scratch options
> successfully in Sync-UI, which I thought were the same as the
> command-line refresh options. If that's correct, then it seems that
> something else is going on.

Your log file pointed me in the right direction: the recently expanded
DevInf confuses the phone. Basically syncing with Nokia (?) phones is
broken in the development version of SyncEvolution. Other libsynthesis
users are not affected.

I can reproduce the issue here with a Nokia N97 mini. There's nothing
wrong in SyncEvolution's usage of SyncML, it's the implementation in the
phone which is broken. But that doesn't help.

I'm not sure yet how to deal with the issue. The offending data is
generated before the SyncML engine has a chance to identify the peer.

Lukas, do you see a chance to delay responding to a Get command for
DevInf until the end of message processing, when any potentially sent
DevInf from the peer was parsed?

What I am aiming at is:
 - libsynthesis in a SyncML client will always send
   all the extended sync modes; with the Funambol
   workaround in place that works
 - libsynthesis in a SyncML server will only send the
   extended sync modes if the client has sent any
   extended sync modes itself; the 390002 mode is
   sent unconditionally for that purpose

The assumption is that the SyncML server will always have up-to-date
DevInf from a client or will get it in the first message without having
to request it. For libsynthesis<->libsynthesis sync that should work,
except that at the moment the outgoing DevInf in the server is generated
before parsing the incoming one.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.


_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to