I would imagine we consolidate these migration into Gecko by moving data from old cookie jar to the new one. But we shouldn't be checking the phone for that on *every boot*, but create a flag/version for it.
For example, here is how we should be migrate Settings DB, which is left unimplemented... https://bugzilla.mozilla.org/show_bug.cgi?id=1112092 On Mon, Apr 13, 2015 at 7:53 PM, Fernando Jiménez Moreno <[email protected]> wrote: > (cross posted to dev.gaia, keep the discussion on dev.b2g, please) > > Hello folks, > > given that we are planning to move our apps from a packaged (app: schema) to > a hosted (http: / https:) model, I was wondering if any of you already > thought about the data migration process that this would require. If we move > an app to a new origin we will need to move all its associated data like > IndexedDB, localStorage, cookies, granted/denied permission (?) or data from > other APIs like MobileID. Do we have any specific plans? Is there any work > already being done for this? > > Cheers, > > / Fernando > _______________________________________________ > dev-gaia mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-gaia _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
