W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: Synchronous postMessage for Workers?

From: Rick Waldron <waldron.rick@gmail.com>
Date: Thu, 17 Nov 2011 18:17:37 -0500
Message-Id: <CA3BF3F5-2780-43BE-9A08-34D18D8E5CA2@gmail.com>
Cc: Joshua Bell <jsbell@chromium.org>, "public-webapps@w3.org" <public-webapps@w3.org>
To: Glenn Maynard <glenn@zewt.org>


On Nov 17, 2011, at 2:37 PM, Glenn Maynard <glenn@zewt.org> wrote:

> On Thu, Nov 17, 2011 at 2:16 PM, Rick Waldron <waldron.rick@gmail.com> wrote:
> This is counter to the whole premise of Workers, which should be independent of their renderer process and certainly not block themselves while waiting for responses from the renderer (which inherently describes an async behaviour). 
> 
> That's backwards.  The premise is that the renderer (UI) will not be blocked by workers, not that workers won't be blocked by the renderer.

No, it's not. Messaging should not block either process. 

> 
> > Sync apis are sore thumb in GlobalWorkerScope's world.
> 
> I don't know what that means.  Synchronous APIs are one of the major reasons to have Workers in the first place.

Considering the current messaging API and the allowed host APIs, I strongly disagree. 



> 
> -- 
> Glenn Maynard
> 
Received on Thursday, 17 November 2011 23:18:10 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:48 GMT