[Tickets #11612] Re: Broken imap fetch query

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/11612
------------------------------------------------------------------------------
  Ticket             | 11612
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Broken imap fetch query
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2012-10-31 22:31) wrote:

> This should fix.  Not used anywhere in imp, so I am assuming this is  
> activesync code

Yes, this is activesync.

> FYI: depending on what you are doing with this return, it may be  
> much faster to use STATUS_SYNCFLAGUIDS and/or STATUS_SYNCVANISHED  
> instead - if using Imap_Client's cache, this methods eliminate 1-2  
> calls to the remote server.

Thanks for the tip. At the point in the code where this is (was)  
happening, I need to know about new/changed messages as well as  
vanished messages. For the changed messages I need the actual state of  
any flags so I don't think I can use the STAUS_SYNCFLAGUIDS. I might  
be able to make use of the STATUS_SYNCVANISHED value, as well as tweak  
other parts of the code where I am only "pinging" the server to check  
for the existence of a change without needed to know what the change is.