[SyncEvolution] How is "peer.config" selected in dbus method Connect

Hello Patrick If the syncevo-dbus-server is supposed to work as a syncML server, the dus api Server.connect need peer.config to be set explictly to select the appropriate configuration. I noticed the http server now uses the request url path to identify this. How can this be handled in obexd? The only possible information Obexd can get without looking into the message is the peer's Mac address, but this property seems not appropriate for configuration identification (The same device can have multiple remote configuraitons). I am asking this because I am using Obexd+SyncEvolution Server <--> Obex Client+client-test for the obex transport test. It looks not easy for the obexd to set the peer.config properly without looking into the message; therefore either it always stick to a default configuration or the server need some other mechanism to detect the configuraitons itself. Also, the documentation seems have not updated to include peer.config. -- Regards, Chen Congwu Moblin China Development