Feature #56298
Cache parameters API
50%
Description
This extension could offer a generic cache parameters API. This ensures centralized management and avoids re-implementations in various context types. The purpose of this is to allow context types to easily add additional cache parameters which increase uniqueness of cached page versions.
The API for adding cache parameters could be put into Tx_Contexts_Context_Abstract and evaluated by Tx_Contexts_Context_Container. It should then be quite easy to extend the hash base creation in Tx_Contexts_Service_Page.
History
#1
Updated by Mathias Brodala over 5 years ago
Updated by - Assignee set to Mathias Brodala
#2
Updated by Mathias Brodala over 5 years ago
- % Done changed from 0 to 50
#3
Updated by Mathias Brodala over 5 years ago
#4
Updated by Christian Weiske over 5 years ago
Updated by - Status changed from New to Rejected
We don't need this patch; I solved the GET-parameters problem in a different way.
#5
Updated by Mathias Brodala over 5 years ago
Christian Weiske wrote:
We don't need this patch; I solved the GET-parameters problem in a different way.
See my comment on Github what this patch is actually for.
#6
Updated by Mathias Brodala over 5 years ago
Mathias Brodala wrote:
Christian Weiske wrote:
We don't need this patch; I solved the GET-parameters problem in a different way.
See my comment on Github what this patch is actually for.
This patch is indeed unnecessary since the list of matched contexts is indeed already unique enough for determining the page cache version.