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? regards, Hans de Jonge
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
