Gaia/Architecture Proposal: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 428: Line 428:
Not at all. With service workers we will have the chance to dynamically cache application resources for offline usage, so once these caches are populated all the requests to fetch app resources will consume the local offline content instead of going to the network, just like it happens with packaged apps. For preinstalled apps we can do an initial population of these caches just like we did with AppCache in the early days of Gaia and so there won't be any data consumption for the initial population of the offline cache. We will have the same scenario as we have with packaged apps in this case.
Not at all. With service workers we will have the chance to dynamically cache application resources for offline usage, so once these caches are populated all the requests to fetch app resources will consume the local offline content instead of going to the network, just like it happens with packaged apps. For preinstalled apps we can do an initial population of these caches just like we did with AppCache in the early days of Gaia and so there won't be any data consumption for the initial population of the offline cache. We will have the same scenario as we have with packaged apps in this case.
Moreover, the current proposal enables us to implement a more clever updates strategy that should mean less network consumption for application updates. If we can download only the resources or even the resource diffs that changed in the server instead of downloading the whole set of application resources on each update like we currently do with packaged apps, we will be consuming far less data from the network and so the cost of updates should be drastically reduced.
Moreover, the current proposal enables us to implement a more clever updates strategy that should mean less network consumption for application updates. If we can download only the resources or even the resource diffs that changed in the server instead of downloading the whole set of application resources on each update like we currently do with packaged apps, we will be consuming far less data from the network and so the cost of updates should be drastically reduced.
== What about the security model? ==
This new architecture requires a new security model. However we are still unsure how this new model will look like. There are some ongoing work and discussions about this that you can follow on these links:
* [[Security/B2G/PermissionReview|https://wiki.mozilla.org/Security/B2G/PermissionReview]]
* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1F-3jAfMPCIqTZzk-CeoK-WuHfFJp9QhEjh6cJ2nVyDE/edit#gid=0 Permissions analysis]
* [https://groups.google.com/forum/#!topic/mozilla.dev.webapi/PicfHG9Figk Proposal: TrustedCache as an alternative to signed packaged apps]
* [https://groups.google.com/forum/#!topic/mozilla.dev.webapi/pCY77YAg_i4  Proposal: Privileged Hosted Apps ]
* [https://groups.google.com/forum/#!topic/mozilla.dev.b2g/UB1CFnVy0mc  Apps and Sensitive APIs ]
* [https://groups.google.com/d/msg/mozilla.dev.gaia/TTl90CZoOvg/eaLTf_iIde4J Delta Updates vs. Signed Resources]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1036275 Support http-served packaged HTML pages/apps]
Confirmed users
483

edits

Navigation menu