[Tickets #11590] Re: Kolab backend: IMAP cache does not get updated
bugs at horde.org
bugs at horde.org
Mon Nov 5 15:57:33 UTC 2012
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/11590
------------------------------------------------------------------------------
Ticket | 11590
Updated By | Thomas Jarosch <thomas.jarosch at intra2net.com>
Summary | Kolab backend: IMAP cache does not get updated
Queue | Horde Framework Packages
Version | Git master
Type | Bug
State | Assigned
Priority | 3. High
Milestone |
Patch |
Owners | Gunnar Wrobel
------------------------------------------------------------------------------
Thomas Jarosch <thomas.jarosch at intra2net.com> (2012-11-05 15:57) wrote:
> This is currently the expected behavior as the implemented
> synchronization strategy is pretty dumb. The old code had no
> synchronization strategy and so it always synchronized the data on
> access. You should be able to go back to the old behavior by
> modifying Horde/Kolab/Storage/Synchronization.php. Add a "if (false
> && ..." to both conditionals present in that file. Does that revert
> back to the expected behavior?
Ok, I understand why the old behavior is inappropriate for many
folders "subscribed" at the same time. The new strategy is quite a
change to H4, we probably should have mentioned it in the changelog.
> I lack a final plan concerning the synchronization strategy
For plain dumb IMAP, what about syncing the folders every XX minutes
(+ random threshold to distribute the server load a bit better)? Also
on login and folder "subscribe".
The sync time should be user configurable, may be 5 minutes as default.
> What describe - concurrent access with two clients to the same
> folder - is not the default case after all. At least not for
> personal folders.
For the "groupware" case it's the default. For example a secretary
managing appointments for another person.
More information about the bugs
mailing list