[Tickets #11590] Re: Kolab backend: IMAP cache does not get updated

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/11590
------------------------------------------------------------------------------
  Ticket             | 11590
  Updated By         | Gunnar Wrobel <wrobel at horde.org>
  Summary            | Kolab backend: IMAP cache does not get updated
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
-State              | Assigned
+State              | Feedback
  Priority           | 3. High
  Milestone          |
  Patch              |
  Owners             | Gunnar Wrobel
------------------------------------------------------------------------------


Gunnar Wrobel <wrobel at horde.org> (2012-11-22 20:25) wrote:

Thanks for the patch. I don't think the "Sync once per session"  
strategy is completely wrong though and makes sense in situations  
where Horde is the primary Kolab client and there is no  
synchronization with other clients necessary. So I did not want to  
simply overwrite it with the new time based strategy. Instead I added  
both. As discussed here there should probably additional strategies in  
the future that would rely on advanced IMAP features.

The time-based strategy holds the core of your patch now. I only  
removed the "protection against clock jumps". If you are logged in to  
a server where the clock suddenly jumps backward the missing  
synchronization with other Kolab clients is the least of my worries ;)  
-> simply log out and you are fine again.

What is missing now is the selection (and potential configuration) of  
the strategy within Horde/Kolab/Storage/Factory.php. In the long run I  
would probably prefer to have a Kolab specific user preference.   For  
now I guess it should be server-wide based on a configuration value  
though. Can you prepare such a patch?