I think we should be really reluctant to add a synchronous interface to an API that has to communicate cross-process.
Feedback from your Inter-App communication and Web Activities folks would be really great! Jeffrey 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. > > 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. > > > Jake Leichtling | Associate Product Manager ☰ Chrome Apps | > jleichtl...@google.com | (415) 279-4508 > > On Tue, Dec 9, 2014 at 9:34 PM, Bobby Holley <bobbyhol...@gmail.com> > wrote: > >> This API is message-passing only, and doesn't have any synchronous >> pieces, right? >> >> What, from your understanding, are the key/interesting high-level pieces >> of this API that need to be sorted out? >> >> On Tue, Dec 9, 2014 at 9:21 PM, Nikhil Marathe <nsm.nik...@gmail.com> >> wrote: >> >>> (cross posted dev.b2g since this seems very relevant to it, but please >>> keep >>> the discussion on dev.platform) >>> >>> Hi All, >>> >>> As part of the ServiceWorker initiative [1], Google is proposing a >>> `navigator.connect` API [2] to allow cross-origin ServiceWorker >>> communication. This post is mostly a notice to inform everyone of this >>> unofficial draft API. >>> >>> This seems similar to our Inter-App communication API [3] and I'm sure >>> the >>> authors and users of that API have feedback that should be incorporated >>> in >>> a cross-web (non-b2g-specific) API. There also seems to be overlap with >>> some use-cases for Web Activities [4]. >>> >>> This is a good opportunity for us to influence how cross-origin messaging >>> is implemented at an early stage. If someone wants to drive this from >>> Mozilla's side, please "raise your hand". >>> >>> Best, >>> Nikhil >>> >>> [1]: >>> >>> https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html >>> [2]: https://github.com/mkruisselbrink/navigator-connect >>> [3]: https://bugzilla.mozilla.org/show_bug.cgi?id=876397 >>> [4]: https://developer.mozilla.org/en-US/docs/Web/API/Web_Activities >>> _______________________________________________ >>> dev-platform mailing list >>> dev-platform@lists.mozilla.org >>> https://lists.mozilla.org/listinfo/dev-platform >>> >> >> > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
