Tickets :: Comment on [#12729] Throttle new mail queries

* Your Email Address
* Spam protection	Enter the letters below: .___.__ __.._..___ [__ [__)(__ \| [__ [___[__).__)_\|_\|
Comment	>> I disagree with some of this. >> >> Calendars can come from any source; internal to kronolith, >> listTimeObjects, remote calendars, etc... Rolling all of these up >> into one listEvents call would prevent the UI from displaying any >> entries until ALL of the results are returned from all of the >> calendar providers. Remote calendars, especially, could slow the >> process down. IMO, it's better to update the UI quicker with the >> locally stored calendars while waiting for any slower calendars to >> load. >> >> If anything, we might be able to batch all "external", "remote" and >> "internal" providers into separate calls, but not everything into a >> single monster listEvents call. > > That's exactly the reason why I replaced the single > Kronolith::listEvents() call from the basic interface with individual > Kronolith_Driver::listEvents() calls for the dynamic interface. > > This issue doesn't have anything to do with listEvents calls anyway, > this should be cached (or rather skipped) with some sane TTL in > IMP_Notification_Handler_Decorator_NewmailNotify instead.
Attachment
Watch this ticket