On Mi, 2011-05-18 at 22:04 +0100, Hans de Jonge wrote: > Op dinsdag 17 mei 2011 17:26:36 schreef Patrick Ohly: > > On Di, 2011-05-17 at 15:53 +0100, Hans de Jonge wrote: > > > [client] > > > client-arch = i386 (BT sync with N900 is working) > > > > > > @Client(client-IP=192.168.6.3): > > > [hansdej]>syncevolution --print-config -q server|grep -v "^#" > > > syncURL = http://192.168.6.2:9000/syncevolution > > > username = hansdej > > > password = - > > > PeerIsClient = 1 > > > > That should be zero. The peer is a SyncML server. > > Aha, that fixed the SoupMessage error and I got some synchronisation indeed: > Thanks > > I am left with a "why" wondering: > In previous experience with the builtin N900 SyncML-Server synchronisation > worked with this parameter like this. I found this a bit couterintuitive > indeed, but it worked and I had accepted as a fait-accompli, Hence I did not > spot it here until you pointed it out. Is this a libsoup specific option and > hence works differently with the Builtin N900 SyncML-server?
No, this has nothing to do with libsoup. The setting merely tells SyncEvolution whether it has to act as SyncML server or client. When talking to a Bluetooth device (like the N900), SyncEvolution is the server. There is no SyncML server on the N900 in this use case. When talking to a SyncML server over HTTP, SyncEvolution is the client. -- 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
