With SyncML Server/Obex client binding, we need to send a SAN package first before doing actual sync session, my suggestion is:
Add ServerAlertSync = 1 in the configuration and if it is set, SyncContext should first call SendSan() before going to doSync(). SyncContext::SendSan() will read configuration from server config, generate the San package, send it with the transport agent and wait for a reply. The reply will be treated as the first package feed to synthesis engine. There need another extention for the configuration too: we need both remote peer address(used to create the transport, call it syncClientURL) and server syncURL (used to tell the client as part of the SAN, call it syncServerURL). The existing syncURL property is more appropriate for syncServerURL. syncClientURL is something the current configuration missed and is more appropriate to be discoverd dynamically (via Bluetooth service discovery). I suggest add "SANPeerURL" property: the property should be set manually now and be set on the fly automatically later via some service discovery magic. -- Regards, Chen Congwu Moblin China Development _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
