[Tickets #12729] Re: Pool multiple requests

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12729
------------------------------------------------------------------------------
  Ticket             | 12729
  Updated By         | Jan Schneider <jan at horde.org>
  Summary            | Pool multiple requests
  Queue              | Kronolith
  Version            | Git master
  Type               | Enhancement
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2013-10-14 15:48) wrote:

> 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.