Confirmed users
764
edits
Firefox/Projects/Jetpack: Difference between revisions
Jump to navigation
Jump to search
→Background
| Line 12: | Line 12: | ||
* The reboot is basically a toolchain, runtime, and API -- a framework. | * The reboot is basically a toolchain, runtime, and API -- a framework. | ||
* "[[Labs/Jetpack/Reboot/Glossary|Cuddlefish]]" is what Atul has coined this framework. | * "[[Labs/Jetpack/Reboot/Glossary|Cuddlefish]]" is what Atul has coined this framework. | ||
* The reboot is very loosely integrated with Firefox. The runtime is bundled in each XPI. The only significant hook that these XPIs require is a [https://bugzilla.mozilla.org/show_bug.cgi?id=542385 | * The reboot is very loosely integrated with Firefox. The runtime is bundled in each XPI. The only significant hook that these XPIs require is a [https://bugzilla.mozilla.org/show_bug.cgi?id=542385 (re)loadable extension mechanism]. | ||
* The reboot has a security model, the prototype didn't. | * The reboot has a security model, the prototype didn't. | ||
* Roughly speaking, there are two layers of APIs under the reboot. There's a low-level, chrome-privileged layer that wraps the platform. And there's a high-level, secure, low surface area, and friendly layer that builds on the lower. It's the higher layer that might be thought of as "the Jetpack API," but it's entirely possible to use the lower to build an extension. | * Roughly speaking, there are two layers of APIs under the reboot. There's a low-level, chrome-privileged layer that wraps the platform. And there's a high-level, secure, low surface area, and friendly layer that builds on the lower. It's the higher layer that might be thought of as "the Jetpack API," but it's entirely possible to use the lower to build an extension. | ||