[Syncevolution-issues] [Bug 6175] Implement client side Server Alerted Sync handling
http://bugzilla.moblin.org/show_bug.cgi?id=6175
--- Comment #9 from pohly <patrick.ohly(a)intel.com> 2010-03-12 06:41:32 PST ---
(In reply to comment #8)
The patch is available in mb6175,
Not merged yet. The patch about "Disable ForceSlowSync if the sync session is
triggered by a remote peer" needs a bit more work. First, the commit message
doesn't explain why this is done and what the pros and cons of the change are.
I remember that we discussed that, but I don't remember the details. Even if
the commit had included a Bugzilla bug number (which I think doesn't exist in
that case), it would still be worthwhile to summarize the discussion.
Second, the patch modifies the signature of sync(), which is the D-Bus
Session.Sync() implementation. In other words, it breaks D-Bus compatibility.
This needs to be solved differently.
one thing I found is using SyncEvolution
template, I have to set auth type to "basic" to get it pass. I think the
authentication process with md5 might be problematic,
It should be disabled when using Bluetooth: the server should get a
mustAuthenticate=false, set username/password to empty temporarily for that
client's sync session and then accept any kind of credentials. Is that not
working anymore?
--
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.