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

basically signal will came from controller, so lots of case we need not to care about class of Signal.
but, controller are instantiate explicitly by developer.

```js
const controller = new AbortController(); // explicit
const signal = controller.signal; // inplicit

controller.abort() // only for abort usage
```

`AbortController` and `abort()` is only for Abort.
more generic API's seems extensible for me..

```js
controller = new TaskController();
signal = controller.signal

signal.addEventListener('any', ...)
controller.dispatchSignal('any', ...)
```

'abort' ing task is one use-case of 'abort' instead of 'any'.

-- 
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-315991108

Received on Tuesday, 18 July 2017 08:12:18 UTC