On Tue, Dec 9, 2014 at 11:04 PM, Jake Leichtling <jleichtl...@google.com> wrote:
> As the draft API spec <http://mkruisselbrink.github.io/navigator-connect/> > currently > stands, initial connection and ongoing communication are all asynchronous. > This is how we have initially envisioned the API, but there isn't any major > impediment to considering a synchronous piece if a compelling use case > supports it. > Synchronous pieces are basically a non-starter IMO, which is why I wanted to double-check that this was async. One key part of the API that remains to be sorted out is what will happen > when a web origin attempts to connect to a Service Worker that is not > registered. This connection attempt could either fail—perhaps without any > indication of whether the SW was not installed or rather the connection was > rejected for some other reason—or it could lead to downloading and > registering the SW. Maybe this scenario necessitates UI in some cases. This > is very much an open question. > Ok. That kind of stuff isn't really my domain, so somebody else on the Mozilla side should pick this up. Overholt - if nobody jumps on this, can you follow up and make sure that we make an explicit decision about what to do here? Cheers, bholley _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
