ryanthompson - 5 days ago
Something I would like to include in a (now likely) v3.6 is this:
We would need to do it there given that we already handle some middleware and HTTP kernel ourselves. Otherwise nothing breaks but the cache does not come into play.
I feel like this would need an interface of some kind to control? Ideas on controlling this in general.. maybe a filtering system instead of per page/post or the module itself.
I see a system to allow you do do like:
/posts -> 60 minute ttl /posts/* -> 60 minute ttl
/ -> 120 minute ttl
We would need to support ESI and also we would need to come up with a way to dynamically purge cache like model cache collections. Where posts are updated then purge post related URLs.
Any thoughts on how to best handle this? Cachable interface on streams? Idk. Need ideas!
This discussion is locked.