James M Snell

For an example use case from Cloudflare Workers... First, some background: The fetch [`Request` object](https://fetch.spec.whatwg.org/#request-class) can receive an `AbortSignal` as part of it's initialization. It also has it's own `AbortSignal`...

> It sounds like it might be easier to allow "this's signal" to be undefined if no init.signal was provided. I'm not entirely sure why every request must have a...

Just weighing in, I'm +1 on supporting this both in Node.js and Cloudflare Workers. I'll wait to implement in either until the spec text is drafted up tho. I definitely...

Just updating here. I did put together a quick prototype in Workers (not public, just local dev) to see if there would be any issues here and it all seems...

After having just gone through the implementation for Node.js core, I'd definitely be +1 on a `disturbed` property on `ReadableStream`. It wouldn't necessarily stop us from creating new Readers if...

I think having a simple `TimeoutAbortController` type would be nice, but not critical. ```js class TimeoutAbortController extends AbortController { /* ... */ } auto controller = new TimeoutAbortController(10 * 1000);...

Thinking about this more. I think what I'd like to see here are several additional APIs for both `AbortController` and `AbortSignal`. * `AbortController.prototype.cancel()` (or `.close()`) -- Indicates that the `AbortSignal`...

I plan to implement this for Node.js and (eventually) Cloudflare Workers, so consider both of those runtimes as in support.

This is closely similar to https://github.com/whatwg/streams/issues/1143 ... Given the choice between `readFully()` and `readAtLeast()` ... we definitely have a preference for `readAtLeast()` ...

@domenic @annevk ... any thoughts on this?