[Tickets #13279] Re: Improve caching of events in daily / weekly view

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/13279
------------------------------------------------------------------------------
  Ticket             | 13279
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Improve caching of events in daily / weekly view
  Queue              | Kronolith
  Version            | Git master
  Type               | Enhancement
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2016-01-28 15:26) wrote:


> Maybe we could pre-fetch the next (as in later) time range of the  
> current view, once all calendars have finished loading. This way we  
> don't slow down the original loading on backends that support  
> time-range requests, but still speed up the most common navigation  
> pattern: moving forward. Zooming out to a larger time range would  
> still have to fill up the missing time slots, but at least that's a  
> comprise.

+1

>> How is the client cache currently invalidated / how does it know a
>> new event was added by someone else?
>
> Not at all. Kronolith on H6 has a refresh button though. We would  
> need to track the calendar history, additionally to the event  
> history, to allow synchronization of calendars to the ajax frontend.

FWIW, I had started working towards this a looong time ago, but other  
projects took my time. I'd still like to eventually get this  
implemented when I have the time...