Asynchronously executing a request should queue a task to fire events

[nox]

As far as I understand, the steps to asynchronously execute a request run outside of the event loop from where the request was created. Given that fact, how can steps 8 and 9 respectively fire an error event and fire a success event?

[inexorabletash]

Yep, that needs fixing.

Thank you very much for looking at the spec at this level of detail. V1 was even less precise and I'd really like to get v2 up to snuff. Your reports like this are incredibly helpful. Keep them coming!

[inexorabletash]

Please take a look at the changes (I touched a few other algorithms that had "fire an event" from a non-event loop context)

It may be more precise (necessary?) to specify e.g. "...queue a task within the task source associated with the request/connection..." in these cases. Suggestions (or examples from other specs) of appropriate text is appreciated.

[nox]

This looks ok, thanks for the quick correction!