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, <bugzi...@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.n...@w3.org > ReportedBy: pablo.cas...@microsoft.com > QAContact: member-webapi-...@w3.org > CC: m...@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. > >