zlacker

>>tinuvi+(OP)
I appreciate the idea, but as others have mentioned it seems like for something like this to be useful it really needs to be well thought out and tolerant to extreme spikes in traffic.

I might be wrong here but it looked like the responses from the server are chunked, which I _think_ precludes the use of a highly optimized cache response e.g. from a CDN. Assuming that's true (very open to correction of course!) I wonder why this would be.

>>shoele+8c1
The web app has a 5-minute cache on dynamic content - which balances info freshness with performance. The architecture supports the ultra-light, fast-loading requirements by design.