Am Dienstag 03 April 2012, um 10:52:00 schrieb Christian Hilberg:
> Hi everyone.
> [...]
> Effectively, I am lacking a mechanism which tells my backend that the user
> wants to synchronize the local cache (evolution implements a full offline
^^^^^^^^^-- evolution-kolab
> cache with offline-editing support) with the Kolab server side. If the network
> is unavailable and then becomes available, it is debatable whether this would
> be a good time to start a synchronization run.
> [...]
> Kolab server synchronization can become quite bulky, since the Kolab server does
> not have some notion of per-client changesets. It is a mere storage, and
> synchronization means to grovel through folders in search of emails. This can
> take quite some time, depending on how many objects are stored in a given folder,
> and it can be heavy on CPU usage as well as network bandwidth usage. If that starts
> grovelling just the moment some network becomes available, that can be much
> annoying to the unexpecting user.
Searching for synchronization conflicts can even involve the necessity to download and
unpack MIME mails and parse the Kolab XML part therein, to find out whether a sync conflict
actually happened - the server does not help us much with this, it is all on the client.
That's one reason why the synchronization with a Kolab server can be bulky. If a sync run
gets cancelled or otherwise interrupted, there is nothing we can do but to start over
and re-do from start.
> [...]
Kind regards,
Christian
--
kernel concepts GmbH Tel: +49-271-771091-14
Sieghuetter Hauptweg 48
D-57072 Siegen
http://www.kernelconcepts.de/
Attachment:
signature.asc
Description: This is a digitally signed message part.