[whatwg/streams] Using fetch streams API without recursion (#958)

Hello,

I'm using the Streams API and have only encountered tutorials / examples which use recursion.  I'm running into a problem which **may** still have the potential to improve the Streams API standard.

I have found that the depth of my code's recursion depends on a variable factor: the chunk/frame size of data sent from the server.  More pointedly, a small delay between broadcasts to the client - the deeper the streams API recursion goes.

In my particular application of the Streams API, I may too easily run into the recursion limits imposed by browsers.

How can I use the Streams API without recursion?  

Full details of my problem and an attempt at a solution (iterative use of the Streams API) are currently documented in this Stack Overflow question:

https://stackoverflow.com/questions/52771970/use-fetch-streams-api-to-consume-chunked-data-asynchronously-without-using-recur

I'd greatly appreciate any pointers you can give me - I'm new to this, so it may be staring me in the face?

QA

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/958