Explore options in changing the reader/writer and endpoint apis to stream payloads, rather than fully construct them. This is likely to be a breaking change, especially if calls were to be split across multiple websocket frames (or across multiple message events over a MessagePort, etc).
This has some potential to reduce latency, but also save memory on both sides by not requiring that the payload (or intermediate products) be kept in memory while finishing writing or reading.
This would likely be a breaking API change for reader/writer and endpoint APIs. Streaming http calls would require #39 as well.
Inspired by gwtproject/gwt#9779.
Explore options in changing the reader/writer and endpoint apis to stream payloads, rather than fully construct them. This is likely to be a breaking change, especially if calls were to be split across multiple websocket frames (or across multiple message events over a MessagePort, etc).
This has some potential to reduce latency, but also save memory on both sides by not requiring that the payload (or intermediate products) be kept in memory while finishing writing or reading.
This would likely be a breaking API change for reader/writer and endpoint APIs. Streaming http calls would require #39 as well.
Inspired by gwtproject/gwt#9779.