--- Comment #10 from pohly <patrick.ohly(a)intel.com> 2010-01-19 00:17:48 PST ---
(In reply to comment #9)
The code is OK for me.
The problem with this solution is: - the whole session must be aborted to avoid
a 222 Alert loop
Why does this problem arise, could you explain?
The commit message you refer to implements one part of the overall solution.
The aborting part was added later. I don't remember exactly why I got the 222
Alert loop, though.
So with the current approach, first time sync is not handled and can
reliability detected? Thus users need to handle this explicitly.
Only if they have local data. If they have no local data, the slow sync is done
as expected. We could detect a first-time sync, but it really isn't that
different from an unexpected slow sync: the user might still want to avoid the
matching of items on the server by doing a refresh sync instead.
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.