The 0.1.0-rc1 release of ezsystems/ezplatform-http-cache is only partially integrated into the kernel.
While it overrides the signal slots and response tagging mechanisms, it does not override the purge client, and does not customize AppCache to use the TagAwareStore.
Definition of done: when the package is enabled:
- content view responses are tagged according to the multi-tagging specification
- http cache is stored by the TagAwareStore
- repository operations purge the stored HTTP cache