[Syncevolution-issues] [Bug 6175] Implement client side Server Alerted Sync handling
http://bugzilla.moblin.org/show_bug.cgi?id=6175
--- Comment #4 from Chen Congwu <congwu.chen(a)intel.com> 2010-03-07 23:43:39 PST
---
(In reply to comment #1)
(In reply to comment #0)
> With obex/bluetooth as the transport, Server Alerted Sync is used, the sync is
> initiated from sync server by a SAN (Server Alerted Notification) request.
SAN *messages* were already accepted for starting a sync. Handling of the SAN
message *content* was added in the meantime.
There are two TODOs left:
// TODO: create a suitable configuration automatically?!
We need to decide what the use cases for this are and which kind of servers we
want to support. Nokia PC Suite? iSync? Our own SyncEvolution?!
Let's support
SyncEvolution first.
// TODO: use the session ID set by the server if non-null
Testing of this feature depends on the deciding about the required server
support.
In SyncEvolution, the session ID in SAN currently is fixed as
"1", because this
part of code is not accessed from syncevo-dbus-server which manages the session
ID. From a command line point of view, the session ID is meaning less and "1"
is OK.
We can support this via querying the session management from dbus server, but
does it has any benefits? (I don't see in SyncEvolution case)
--
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.