Abstract
This article presents a practical guide to using HTTP streaming for efficient data visualization in web applications.
I was i...
For further actions, you may consider blocking this person and/or reporting abuse
I found this article to be very well written.
I’m excited to do some generator benchmarking against my byte-barometer. I haven’t done a write up yet but feel free to give it a try.
chahla.net/static/byte-barometer/
Great article, I found it very interesting.
I would love to see a comparison, to think about the pros and cons of using HTTP streaming against Servers sent events or websockets communication
Interesting topic
I think that SSE and/or WebSocket fit for different (and more complex) scenarios when user interactions are thought purely in asynchronous fashion, while streaming is mostly an optimization to improve the overall user experience minimizing the negative impact upon waiting of data
Great , can i work with json as Content-Type?
Absolutely yes
Simply to have to change content-type accordingly and parse JSON after client decoding
Take in account that you are responsible to produce from the server a valid JSON chunk of data
Isn't using await counterintuitive to streaming ?
Await means, wait for the api call to finish, then proceed
Await is needed because we expect that chunk of data is ready, the asynchronous iterator is used for this purpose.
At the end you have multiple await and for each of them the chunk of data produced is returned to the client.