Currently, Gecko's workers are limited in terms of functionality because
many bindings use XPConnect but only new JSClass/Paris-style bindings
can be exposed. See https://bugzilla.mozilla.org/show_bug.cgi?id=580070
for more on that.
Is it our plan to expose all of our WebAPI's to Web Workers, or only a
subset?
The background for my question is that we are currently trying to move
much of the e-mail back-end into a worker. (A background page would
have been preferred but those aren't really supported and would
introduce too many edge cases at the current time.) For
https://bugzilla.mozilla.org/show_bug.cgi?id=832824 we want to resolve
e-mail addresses to contacts from the mozContacts WebAPI. This is
something that could be done in the mail libs back-end on the worker, on
the front-end side of the mail libs 'bridge' in the main page itself, or
something the Gaia e-mail UI could do on its own. The right choice for
the medium future depends on whether mozContacts will eventually be
available on the worker or not. (In the long-term, the back-end will
want to know about contacts to support advanced features, no matter what.)
Andrew
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
