ok, thanks Ben
Of course you have the right to continue however you like, but :) it
would be ultimately nice to just have one great caching solution.
Especially for users its usually hard to figure out what to choose if
there are several solutions. So maybe once you're further down the road
with your approach we should try to join forces with the ACS people and
see whether we can maybe combine the approaches. If they are totally
different and if it makes sense to have two solutions, then that's fine
too.
Carsten
Am 05.09.2019 um 08:30 schrieb Ben Zahler:
Hi Carsten, hi Dan,
A short update: David Gonzalez, who is driving the ACS AEM Commons HTTP Cache
project, just confirmed:
"once it serves from cache (request or resource include) nothing within that caches
response is modifiable(outside transformer pipelines). it just streams that chunk of data
to the response."
So I think the ACS AEM Commons HTTP Cache is quite different from my approach
and is not what I'm looking for. For now, I'll just continue to work on my code
and try to get it to a point, where it's ready to be used in the real world.
Let me know if you have any additional input or if you're interested in trying
the cache in your environment.
Regards,
Ben
--
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
