[Tickets #12589] Re: Kolab_Storage: Ensure status($folder) is not cached

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12589
------------------------------------------------------------------------------
  Ticket             | 12589
  Updated By         | Thomas Jarosch <thomas.jarosch at intra2net.com>
  Summary            | Kolab_Storage: Ensure status($folder) is not cached
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             | Jan Schneider
------------------------------------------------------------------------------


Thomas Jarosch <thomas.jarosch at intra2net.com> (2013-08-23 07:28) wrote:

>> I could see adding something like a global "Long-running script" flag
>> to the base IMAP object that would indicate that the object is being
>> used in a long-running script and STATUS_FORCE_REFRESH should be used
>> on every status() call.
>
> This has been added.  To disable status() caching,  
> Horde_Imap_Client_Base:$statuscache should be set to false.

Thanks! Please take a look at the change again, I think you  
accidentally added the wrong flag.
(STATUS_UIDNEXT_FORCE instead of STATUS_FORCE_REFRESH).

Hmm, I'm still not sure if this is the ideal solution. As you pointed  
out earlier,
this might cause more round trips to the imap server than necessary.

If we look at the search() function for example, in the "long running  
script mode"
it would issue a STATUS command to the server and based on that
result send a SEARCH command or not. In that case it would be better
to just send the SEARCH directly.

I think for most use-cases of long running scripts, the new
STATUS_FORCE_REFRESH flag will do the job just fine as the
library users can decide when to use caching and when not.