Question about `Stream.runForEach` Concurrency and Fiber Forking
Is
Context:
I'm trying to make a quick WebTransport server using the
My plan is to wrap the
Stream.runForEach concurrent or should I fork the fiber?Context:
I'm trying to make a quick WebTransport server using the
@fails-components/webtransport package, but they only provide a streams based API (so no session callback available) which makes managing concurrent sessions painful (creating promises doesn't ensure those promises are awaited/canceled when closing, and I don't want to create a system for tracking live promises).My plan is to wrap the
ReadableStreamStream, then handle each session concurrently. So would I need to fork the fiber (I'm guessing yes)?
