7:28 a.m.
On Sat, 2010-05-15 at 10:35 +0100, Anssi Saari wrote:
Patrick Ohly <patrick.ohly(a)intel.com> writes:
> Funambol is one option, but IMHO overkill. I'd go for an installation of
> SyncEvolution as HTTP server instead, see
> http://syncevolution.org/development/http-server-howto
I tried to set this up. Following the server setup was easy, but I'm
not really sure how to setup the matching client?
On remote clients simply use the URL that you chose and the URIs listed
at the end of the document under "Setup of Client(s)" (addressbook,
calendar, ...). For SyncEvolution as client, use the "SyncEvolution
Client" configuration template.
Maybe you should
have a document for that too. For example, I found out that one needs
to run with --daemon=no in the list archives, before I knew that
syncevolution just sat there until its two minute timeout triggered.
Now that sounds like you are running SyncEvolution server and client on
the same machine; that isn't necessary and as you said, does not work
out of the box.
If you want other clients to synchronize against your local Evolution
data, then don't set "--source-property type" when adding the new client
to the server's config. This is not explained in detail because I am not
entirely sure about the use case - perhaps starting a sync on a client
which cannot be reached via Bluetooth?
But basically I used the scheduleworld template for the client and
then changed the URIs and types to be the same. But all I've managed
to get is this complaint about unexpected slow syncs:
$ syncevolution --daemon=no syncevo_client
[INFO] calendar+todo: inactive
POST from 127.0.0.1 config type application/vnd.syncml+wbxml session None args {} length
7890
requesting new session
SessionChanged: /org/syncevolution/Session/20408408791273914281 1
reply session 20408408791273914281 final 0 data len 8416
dbus.Dictionary({dbus.UTF8String('URL'): dbus.UTF8String('')},
signature=dbus.Signature('ss'))
[INFO] memo: starting first time sync, two-way
[INFO] calendar: starting first time sync, two-way
[INFO] addressbook: starting first time sync, two-way
[INFO] todo: starting first time sync, two-way
[INFO] memo: first time sync done unsuccessfully
[ERROR] memo: unexpected slow sync (local, status 22000)
[INFO] calendar: first time sync done unsuccessfully
[ERROR] calendar: unexpected slow sync (local, status 22000)
[INFO] addressbook: first time sync done unsuccessfully
[ERROR] addressbook: unexpected slow sync (local, status 22000)
[INFO] todo: first time sync done unsuccessfully
[ERROR] todo: unexpected slow sync (local, status 22000)
That's normal. There's more output that explains how to handle this
(choose a different sync mode manually).
--
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.