At a high level this PoC looks similar to
https://adobe-consulting-services.github.io/acs-aem-commons/features/http-cache/index.html
I think it would be good to talk with the people behind that project and
maybe team up to get a single great solution in Sling
Regards
Carsten
Am 03.09.2019 um 09:41 schrieb Carsten Ziegeler:
Hi Ben,
I like the fact that it does not require changes in Sling as this means
it can be used as an add on. Using filters should not add more overhead
than using any other approach more baked into the Sling engine, so from
that perspective I think the solution is fine as well.
If there are requirements to get more information about the request like
gzip compression that you mention, we should find a good way to pass the
info to the place where it is needed. Maybe it makes sense to get a list
of these things and find out how we can handle it
Regards
Carsten
Am 02.09.2019 um 23:15 schrieb Ben Zahler:
Hi Carsten,
Yes, at least for now, I'm completely relying on filters.
I think that approach should work, but there are a few cases where
additional information from sling could help (for example detecting
that gzip compression is applied). I have not looked into that in detail.
That said, unfortunately, I am not familiar with the implementation of
the sling engine, so I don't know if my approach is the best possible
option.
Regards,
Ben
--
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
