A large API response becomes a client problem long before it becomes a network problem. A browser can receive hundreds of megabytes and still become unresponsive while buffering bytes, parsing one enormous JSON document, retaining duplicate object graphs, and rendering too much state on the main thread.
A large API response becomes a client problem long before it becomes a network problem.
It is to stop treating the response as a synchronous document and start treating it as a durable, observable job whose data arrives in bounded pieces.
A browser can receive hundreds of megabytes and still become unresponsive while buffering bytes, parsing one enormous JSON document, retaining duplicate object graphs, and rendering too much state on the...
The page is ready to read now. The fuller skim-friendly version will appear here automatically.
A large API response becomes a client problem long before it becomes a network problem. A browser can receive hundreds of megabytes and still become unresponsive while buffering bytes, parsing one enormous JSON document, retaining duplicate object graphs, and rendering too much state on the main thread. It is to stop treating the response as a synchronous document and start treating it as a durable, observable job whose data arrives in bounded pieces.
The reliable solution is not a larger timeout.
Open the app view to save this story, compare related coverage, and continue from the same source.