Re: [whatwg/dom] Abort controller design (#438)

Overall seems pretty reasonable standalone. I think it'd help to see this in action though by defining the transfer steps for Request that use it.

> (Or should we simply throw? There's not much point to this.)

I wouldn't; it's useful to sometimes pass things around without having to do a state-check and a separate code path.

> (Aside: hopefully we can do better than this.)

Yeah... this and the event listener on the other side really cry out for a better spec-level abstraction for these things. Maybe the port message queue is what should be used here?

It's fine for now though.

> Set serialized.[[IncomingPort]] to ! StructuredSerializeWithTransfer(channel's port2, channel's port2).

Second arg should be a list.

-- 
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/dom/issues/438#issuecomment-301632105