- From: Jeremy Orlow <jorlow@chromium.org>
- Date: Wed, 15 Dec 2010 11:21:20 +0000
- To: public-webapps@w3.org
- Message-ID: <AANLkTiks178aQUydnftQNDUo6-4n=4bfYWuxpARj167P@mail.gmail.com>
I believe the instance of WorkerUtils is much like window in a page. I.e. you put stuff on there that you want in the global scope. Thus I'm pretty sure that WorkerUtils is the right place for both. J On Wed, Dec 15, 2010 at 1:54 AM, <bugzilla@jessica.w3.org> wrote: > http://www.w3.org/Bugs/Public/show_bug.cgi?id=11553 > > Summary: Ensure indexedDBSync is on the right worker interface > Product: WebAppsWG > Version: unspecified > Platform: All > OS/Version: All > Status: NEW > Severity: normal > Priority: P2 > Component: Indexed Database API > AssignedTo: dave.null@w3.org > ReportedBy: pablo.castro@microsoft.com > QAContact: member-webapi-cvs@w3.org > CC: mike@w3.org, public-webapps@w3.org > > > I just noticed that the async part of the spec has indexedDB in Worker > (i.e. > "Worker implements IDBEnvironment"), whereas the sync API has it > WorkerUtils. > The second one is probably just old, so for my current editing pass > (bringing > sync/async in sync) I'll just change it to "Worker" for consistency. > > However, from looking at the Web Workers spec [1] it seems that > IDBEnvironmentSync should be implemented by AbstractWorker so it's > available in > regular and shared workers. Is that right? If not, what's the right spot? > > [1] http://dev.w3.org/html5/workers > > -- > Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. > >
Received on Wednesday, 15 December 2010 11:22:11 UTC