On Thu, Dec 11, 2014 at 5:56 PM, Alex Russell <slightly...@google.com> wrote: >> One solution would be to at that point allow the SW from the other >> origin to install itself, which means that you can then just talk to >> it as a normal installed SW. However installing a SW could take >> significant amount of time. On the order of tens of seconds if the >> user is on a slow connection and the SW represent an app with heavy >> resources. > > I'm OK with it taking time. The discovery phase of a n.c() setup is async.
This is along time though. If the initiating website is holding *any* UX before getting a response you'll end up with a unreasonably bad experience. So for example if cross-site communication is initiated when the user press a button, the response to that button push can take unacceptably long. It also means that we couldn't use SW for WebActivities/WebIntents for example. That seems unfortunate. I don't feel like we're heading down the right design. / Jonas _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
