3 ms·
A while ago I built an app data framework that used similar logic (although a bit more abstracted) to coalesce every GET type request. It made me wonder why ne
by jordansmithnz 8y ago
A while ago I built an app data framework that used similar logic (although a bit more abstracted) to coalesce every GET type request.
It made me wonder why network libraries don’t do this for the actual requests by default (or perhaps they do?). I’m sure there are some cases where simultaneous requests are intentional, but it seems like this would be infrequent.
- skohan 8y agoI guess the argument against would be that it adds complexity for a use-case which is probably infrequent. How often does the average HTTP client request the same resource multiple times concurrently? In what subset of those cases does it actually matter if requests are redundant? Why waste your user's clock-cycles on an edge case?