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

Search Results: 74 of 94 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

* Your Email Address
* Spam protection	Enter the letters below: .__ .__ . .. ..___ \| \\| \\ /\|\ \|[__ \|__/\|__/ \/ \| \\|[___
Comment	> >> 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...
Attachment
Watch this ticket