[Tickets #11305] Kolab storage: Move of objects does not update the cache

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/11305
------------------------------------------------------------------------------
  Ticket             | 11305
  Created By         | Thomas Jarosch <thomas.jarosch at intra2net.com>
  Summary            | Kolab storage: Move of objects does not update the
                     | cache
  Queue              | Horde Framework Packages
  Version            | Git develop
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Thomas Jarosch <thomas.jarosch at intra2net.com> (2012-07-21 17:26) wrote:

Hi,

moving an object in mnemo or nag is currently broken:

The message is moved on the IMAP server but the horde cache is not updated.
This results in a horde exception once the active application tries to  
access it after the move.

Rant of the day:
I've tried for two hours to understand the new code Kolab_Storage code  
structure and still don't fully get the details. Compared to Horde 4,  
the size/complexity of the Kolab backend increased from 14 php files  
to 81 files. Lines of code exploded from 7030 to 18742 (not counting  
the unit tests).

I'm also wondering why we need five different IMAP driver  
implementations in Kolab_Storage?

Cheers,
Thomas