3 ms·

All those sub-page widgets can be pre-computed and, thus, cached. The first web request (at worst) should initiate all those, but you shouldn't be fully comput

• jacques_chester 16y ago
  > All those sub-page widgets can be pre-computed and, thus, cached. That's broadly what I mean by changing the pipeline to be post-focused. When the site has a change pushed to it, the relevant parts should be re-rendered down to HTML for a fast HTTP server to dish up. The current model works the other way. Until somebody does a GET, the system may or may not have the rendered HTML in a cache. Even if it does, it may or may not be a verifiably up-to-date copy. This seems hit-and-miss to me. I've sort of sketched design ideas around this area (using, for example, PostgreSQL triggers and NOTIFY to prompt rendering). Maybe I'll write a blog post, but it's basically pointless without code.