On Mon, 2009-09-21 at 08:28 +0100, Patrick Ohly wrote: > On Mon, 2009-09-21 at 03:27 +0100, Zhao, Forrest wrote: > > Ohly, Patrick wrote: > > Yes, without the support for Server Alerted Notification the syncml > > session can't be created via Bluetooth transport. So I can't test my > > code for OBEX server/SyncML client binding. > > So you already have code? I thought you were just starting with writing > it. Anyway, connection setup can already be tested. I'll look into SAN > today.
I pushed a commit to the D-Bus branch which should be sufficient to run a sync session with syncml-ds-tool: commit d30ae93616989c177eed4c50db772a8d389db3d7 Author: Patrick Ohly <[email protected]> Date: Mon Sep 21 15:25:14 2009 +0200 syncevo-dbus-server: allow SAN messages to start a Connection Server Alerted Notication (SAN) messages (type "application/vnd.syncml.ds.notification") now are accepted in the setup phase of a Connection. The *content* of the message is completely ignored at the moment. A local config called "default" must exist with valid settings for each data source, which is used to to run the sync. Congu suggested the following example command: ./syncml-ds-tool --port BtMac BtChannel --sync text/x-vcard Contacts The corresponding SyncEvolution configuration (which must be created first) can be set up with: syncevolution --configure --template google \ --sync-property enableWBXML=1 \ --source-property type=text/x-vcard \ --source-property uri=Contacts \ default addressbook The template is pretty much arbitrary here, all of the relevant properties are specified on the command line. I'm not sure about using WBXML. If the syncml-ds-tool server works like a HTTP server, then the client can contact it with both XML and WBXML and the server will respond using the same format. In that case, both enableWBXML=1 and enableWBXML=0 will work. This needs to be tested; the obexd plugin should support both Reply content types. -- 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
