Hi,
On my debian testing  machines I am trying to realize syncevolution by 
implementing the http-server howto of the development-pages:

On the server I Issue the commands:
syncevo-dbus-server &
 and 
/usr/bin/syncevo-http-server http://192.168.6.2:9000/syncevolution
(All sources are files configured according to the method I described in my 
post 
at march 23rd)

When I enter the address " http://192.168.6.2:9000/syncevolution"; in browsers 
on both the server(192.168.6.2) and client machine(192.168.6.3) a page 
containing the comforting phrase 
"SyncEvolution SyncML Server"
appears.
When I try to connect (and synchronise) from the client machine, using 
"syncevolution servername" 
the connection fails at an early stage with an error:
"could not allocate SoupMessage"

and not even any reaction on the prompt of the server machine where the 
syncevo-http-server-process is running (e.g. to verify the ID mentioned in 
steps 8-10 of the HOWTO)
Any idea what might be wrong or what I should investigate further to get 
things working?

PS. I want to get this working because:
The Bluetooth-obex solution between the ics-file on computer and N900 is 
failing lately: I cannot get it working from the preferred OS again. From the 
syncevolution pages I got the impression that this is due to a known and 
bug in the BT-NokiaSyncMLserver system outside the scope of syncevolution?  
Also a HTTP route feels more reliable and versatile than BT.

Regards, Hans de Jonge

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to