Closed wlonk closed 8 years ago
Will there be cache busting problems if we are populating the status in the httpresponse?
Overall, looks good to me.
Also, that is a great sloth.
I'll have to look into our caching more; there are, potentially, cache problems there.
I can take a stab at the JS approach if you would like.
Nah, lemme focus on the caching first.
Incidentally, our REST API endpoints had excessive caching. We had no DEFAULT_CACHE_RESPONSE_TIMEOUT
set; see the docs.
I think we can shorten our CACHE_MIDDLEWARE_SECONDS
env variable, too.
(Still investigating caching behavior.)
Looks like it'll be OK? Not super confident in that, but we can always revert in prod if it misbehaves.
I think this is ready to merge and push when you like it.
Per @amirtouray's feedback.
Some hacky untested stuff around showing parser-pipeline status.