On Thu, Dec 11, 2014 at 3:48 PM, Jonas Sicking <jo...@sicking.cc> wrote:
> On Thu, Dec 11, 2014 at 11:17 AM, Alex Russell <slightly...@google.com> > wrote: > > For the purposes of API composition, either this (or navigator.connect()) > > will do. > > One thing that we'll need to solve in a lot of the scenarios discussed > in this thread, including navigator.connect(), cross origin SW fetch() > and WebActivities/WebIntents are how to communicate with the SW from a > different origin when the SW from that origin might not be installed > yet. > I sketched out a solution to this problem with Marijn that uses headers (previously discussed for Service Workers) and I'll update an explainer doc with that option. > 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. > So we might need to enable SWs to handle events without first being > installed. Or maybe while they are being installed. > I don't think that's necessary or advisable. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
