On Thu, 2013-01-24 at 02:31 +0100, Christof Schulze wrote:
I found a couple of remarks from 2010 on the web saying there is a
in the oxtender but at this point I am probably better off, turning to a
It's indeed hard to tell why the server thinks that the session is not
done yet when the client has already quit.
> > Now I do not see a spot where the investigation should be
> > This might be an issue with the data itself, syncevolution, funambol
> > or even a performance issue since syncevolution, funambol and the
> > webdav (owncloud) are running on the same hardware.
> May I ask what you need Funambol for? Perhaps Syncevolution could do
Funambol is used because I want to be able to synchronize my nokia e51
phone to my server at any time from anywhere.
However, and that is what I use syncevolution for, I would also like
my calendar from my nokie e51 to show up in a calendar in my owncloud
instance - hence the syncml-webdav-sync.
If that is possible with less hassle (at the moment it does not work
due to this kind of synchronisation issues) without using funambol -
perfect! What should I read to find out what to set up?
A first starting pointer is the howto for using SyncEvolution itself as
a SyncML server:
The difference is that you don't want to use a local file database in
that SyncML server. Instead you want it to act as a bridge for CalDAV.
That's possible: instead of configuring a SyncML client of the Funambol
server (which you have already working), configure the SyncML server
side for the e51 inside the context where the local database is the
CalDAV source and thus let the e51 talk to Owncloud directly, without
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.