-
Suggestion
-
Resolution: Obsolete
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
It is possible for plugins to do an expensive per-Confluence startup calculation and store the data in the cache. If the plugin can keep the data updated throughout the lifecycle, it would a disadvantage if that calculated data is wiped away automatically every hour.
It would be nice if the plugin could tell the caching system:
"For cache XYZ, don't ever automatically invalidate anything in it"
- blocks
-
CONFSERVER-50112 Make Google Calendar to Team Calendars synchronisation frequency or interval to be configurable
- Gathering Interest
- relates to
-
CONFCLOUD-22493 Allow plugins to define their own caches' attributes
- Closed
-
CONFSERVER-51292 Eliminate lag time between setting date in JIRA field and seeing changes reflected on JIRA calendar
- Gathering Interest
Form Name |
---|
Confluence 5.5 has shipped a new Cache API which allows for more control over any cache you create.
It's not a great idea to have a cache that never expires, but if you need something like this, the new cache api will allow you to set a large expiry time.
I will close the issue as Obsolete assuming this new API covers this use case, feel free to reopen if it does now.