[whatwg] workers

[Aaron Boodman]

2008/9/30 Alexey Proskuryakov <ap at webkit.org>:
> Hmm... So this is more about how you use the interface, not what the object
> behind it is. If one chooses to never call close() on a shared worker (or,
> say, sets myWorker.close to null right after invoking constructor), it
> becomes indistinguishable from a dedicated worker.
>
> Hiding close() possibly sounds more like something a high-level framework
> may want to do to enforce a certain design pattern than a core feature.

I could see that too. When all the parties accessing a shared worker
are from the same origin (as they are today) it is less of an issue.
You can probably assume that they know not to close() the worker.

Do you have any thoughts on the extra API on dedicated workers
proposed by Jonas (DedicatedWorker::sendMessage,
DedicatedWorkerGlobalScope::onmessage)?

- a