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

[whatwg] Workers in HTML5 (was: postMessage apply(), pipe, etc.)

From: Geoffrey Garen <ggaren@apple.com>
Date: Thu, 14 Feb 2008 15:05:38 -0800
Message-ID: <0759127E-0DBE-48FB-AC8B-33EE9ACE4EA2@apple.com>
> Since postMessage API is looking more an more like the Gears worker
> messaging API (or better), can we go one step further and introduce
> workers into the HTML5, defined as invisible windows with limited
> capabilities:

Why call these "windows" at all? They seem to have no relationship  
physical windows, or the JavaScript "window" object.

> WorkerWindow openWorker(in DOMString url);

Can I supply a URL to an HTML file here? Does the file load and parse  
as an HTML document? Is the document accessible to the worker?

Since the whole point of the worker is to do JavaScript work, should  
this string be a script instead of a URL?

How do I pass data to a worker?

Is there an API contract regarding synchronization and/or order of  
execution?

>   // some events
>   attribute EventListener onabort;
>   attribute EventListener onload;
>   attribute EventListener onunload;

Why these events?

When is a worker considered loaded? Unloaded? Aborted?

Thanks,
Geoff
Received on Thursday, 14 February 2008 15:05:38 UTC

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