I believe, but am not sure, that browsers give a separate database for each (sub)domain, so sub1.main.com sees different data than sub2.main.com .
Other than that, it looks like IDBFS just gets a database using the mount point, so changing that would get a separate database I believe. Different apps on the same domain with the same mount point should see the same data. - Alon On Sun, Apr 19, 2015 at 3:57 AM, Mike Arnautov <[email protected]> wrote: > A given app will, reasonably enough, only see the IDBFS-provided file > system specific to itself. But how is it decided *which* IDBFS object > belongs to which app? A bit of experimentation shows that the same app in > different locations is not deemed to be the same app. But there is clearly > more to it than that because two replacing one version of the app with a > different one under the same name is also detected as an app-change. On the > other hand a certain amount of change to the controlling HTML file and to > the C code being converted is tolerated as not constituting an app change. > > So how is access actually determined? What advice do I give my users? > Clearly relocating the app is a bad idea -- one loses any accumulated > persistent data. Is upgrading to a later version safe? At what point does > an upgrade become an app change? > > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
