[MGNLCACHE-37] Cache configuration should be simplified Created: 16/Jan/09 Updated: 03/Feb/16 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Cache Modules |
| Component/s: | configuration |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
It is generally too complex. Will gather feedback on this issue before doing anything about it. |
| Comments |
| Comment by Philipp Bracher [ 22/Jan/09 ] |
|
I agree and I missed the simple 'enabled' property the most. While the voters are really powerful and you can build conditions which cannot be built with boolean expressions (I really tried that hard) we should hide that complexity. In the normal configuration it should be enough to:
What made the current voter configuration so complex is the fact that we wanted the very same configuration for the author and public instances (no separate bootstrap files, save activation, ...). In addition to that we didn't switch of the cache completely on author instances (for resouces, ..). So I used the level feature of the voters heavily and it works quite nice. But now that I have seen how people in general react when they see this configuration I agree that it is time to simplify it. |
| Comment by Magnolia International [ 22/Jan/09 ] |
|
One possibility would be to have a "meta" voter, that is simply hardcoded with the logic we built in the set of default voters, maybe a few simple properties (cacheOnAuthor, that sort of thing) |
| Comment by Philipp Bracher [ 27/Jan/09 ] |
|
Makes sense. |
| Comment by Magnolia International [ 14/Mar/14 ] |
|
Actually, such a "meta voter" has been documented for a while on this concept page - http://wiki.magnolia-cms.com/display/DEV/Concept+-+Cache+Improvements#Concept-CacheImprovements-Globalcachevoter - see the "Global cache voter" paragraph. |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |