Skip to content

feat: Give more control over caching - #40860

Closed
ChristophWurst wants to merge 1 commit into
masterfrom
feat/caching-control
Closed

feat: Give more control over caching#40860
ChristophWurst wants to merge 1 commit into
masterfrom
feat/caching-control

Conversation

@ChristophWurst

Copy link
Copy Markdown
Member

Summary

  • Make it clear when caching is actually available and populating makes sense
  • Add factory method for in-memory caches

This is quick PR putting some ideas around #40800 into code.

Checklist

* Make it clear when caching is actually available and populating it
makes sense
* Add factory method for in-memory caches
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
@ChristophWurstChristophWurst added 2. developing Work in progress feature: caching Related to our caching system: scssCacher, jsCombiner... labels Oct 11, 2023
@ChristophWurstChristophWurst self-assigned this Oct 11, 2023
@solracsfsolracsf added this to the Nextcloud 28 milestone Oct 27, 2023
@skjnldsvskjnldsv mentioned this pull request Nov 1, 2023
@ChristophWurstChristophWurst removed this from the Nextcloud 28 milestone Nov 2, 2023
@ChristophWurst

Copy link
Copy Markdown
MemberAuthor

There are method to check availability before acquiring an instance. This isn't strictly required.

@ChristophWurst
ChristophWurst deleted the feat/caching-control branch November 2, 2023 10:10
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2. developingWork in progressfeature: cachingRelated to our caching system: scssCacher, jsCombiner...

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@ChristophWurst@solracsf