W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2014

Move sync APIs out of "Worker" into "SyncWorker"

From: Jake Archibald <jaffathecake@gmail.com>
Date: Tue, 29 Jul 2014 16:30:51 +0100
Message-ID: <CAJ5xic_1d+=RJtztkGVfCMrv=dA+0jjGyVUWToeeVQzz+0uv-Q@mail.gmail.com>
To: public-script-coord <public-script-coord@w3.org>
Cc: Alex Russell <slightlyoff@google.com>
Over in ServiceWorker we want to get all of the APIs available to workers
(FormData, indexeddb, URL etc), but not the synchronous interfaces such as
http://dev.w3.org/2006/webapi/FileAPI/#readingOnThreads

We could expose each API on ServiceWorker individually, but other
multi-client worker contexts are likely to want to do the same. It could be
argued that filesystem's *Sync methods shouldn't exist in a SharedWorker
scope.

Would it makes sense to do one of the following?:

* Expose the sync methods on DedicatedWorker only - this would require
usage stats of sync methods in SharedWorkers to be insignificant
* Expose the sync methods on a new global SyncWorker, where
DedicatedWorkerGlobalScope would
be [Global=Worker,SyncWorker,DedicatedWorker], SharedWorkerGlobalScope
would be [Global=Worker,SyncWorker,SharedWorker]
Received on Tuesday, 29 July 2014 15:31:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:22 UTC