W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2008

[whatwg] Workers in HTML5

From: Robert O'Callahan <robert@ocallahan.org>
Date: Thu, 21 Feb 2008 11:23:59 +1300
Message-ID: <11e306600802201423i1dd8f241m39800e98ed0eb810@mail.gmail.com>
On Wed, Feb 20, 2008 at 3:05 PM, Maciej Stachowiak <mjs at apple.com> wrote:

> If XMLHttpRequest is one of the APIs available on background threads,
> does that include its XML parsing/serialization features (responseXML
> and the ability to pass a Document as the post data)? If so, then
> effectively the whole DOM API has to be available on the background
> thread, which may increase the implementation complexity a fair bit
> over having only selected APIs available.
>

Having the DOM be available on other threads would be a pretty big
implementation burden for us too. Then there are are DOM APIs like <canvas>,
SVG APIs, etc ... each of those would either have to be disabled on worker
threads or take additional work to make thread-safe (even if the additional
work is just checking code). There's also styles and subresource loading,
which we already disable on XHR data documents but I'm not sure if that's
defined in any spec. Basically this is a very big can of worms you're
opening here...

Rob
-- 
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
53:5-6]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20080221/e32fef35/attachment.htm>
Received on Wednesday, 20 February 2008 14:23:59 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:39 UTC