[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         | athavale.anant at gmail.com <athavale.anant at gmail.com>
  Summary            | Pool multiple requests
  Queue              | Kronolith
  Version            | Git master
  Type               | Enhancement
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2013-10-01 22:10) 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.