[worker] Integration of WorkerGlobalScope and AbstractWorker

• From: Bang Seongbeom <bangseongbeom@hotmail.com>
• Date: Sun, 23 Aug 2015 19:23:07 +0900
• To: public-webapps@w3.org, ian@hixie.ch
• Message-ID: <BLU437-SMTP34BF1E5A03AD6355C0B9F8B0630@phx.gbl>

The current spec says that the internal worker scope is 
WorkerGlobalScope(or Dedi-, Shared-), the external is AbstractWorker(or 
Worker, Shared-.) But it destroys consistency with Window object and 
confuses users with the difference of WorkerGlobalScope and AbstractWorker.

The global scope Window object can't access to the other Window object 
that's derived from the other origin because of the Same Origin Policy. 
Like this, we can restrict the access by it, not to separate the two 
objects.

And it's hard to understand that why can't terminate in 
WorkerGlobalScope and can't close in AbstractWorker. These two methods 
should be provided equally, or not.

Received on Sunday, 23 August 2015 10:24:12 UTC