- Implement better error-handling support for WorkerPools
- Make the onmessage callback optional
WorkerPool.onerror
, then the error should be thrown in the global context of the parent page. Basically, it should do the same thing as what happens when you run this JavaScript code:window.setTimeout("throw new Error('boo!')", 100);
Spidermonkey (the JavaScript engine inside Firefox) has an API that I believe we can use for this purpose: JS_ReportError. I'm not sure if there is an equivalent for IE, or if I will have to basically do something like:
eval("throw new Error('boo!')")
. I would like to avoid using eval if possible because it seems hacky and there are more security considerations.
No comments:
Post a Comment