On Tuesday, June 14, 2016 at 11:51:16 AM UTC+1, Joe Walker wrote: > I don't think you can say "It's sync unless <something> in which case it's > async". > If that's that case then from the API consumers point of view, then (deep > voodoo withstanding) it's async.
As weird as it sounds, I believe that you actually can in this case. Because the API is declarative, we can translate DOM synchronously and if we encounter an error, we can either synchronously or asynchronously get the fallback. Which means that we're only dealing with async (potentially) when we hit an error scenario. Dealing with worse performance in error scenarios is still significantly better than the current situation where we just crash. And as Axel pointed out, we can do the error scenario sync or async, depending on our decisions that don't affect our architecture. zb. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform