1,273
edits
Labs/Jetpack/Reboot/JEP/106: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(added a strawman proposal.) |
Dandonkulous (talk | contribs) No edit summary |
||
| Line 29: | Line 29: | ||
Jetpacks are accessible through the <tt>jetpack:</tt> protocol. Each Jetpack has a keypair associated with it, and a Jetpack's ID is the SHA-1 hash of its public key. Jetpacks must be signed using their private key, and will not be loaded unless signed; thus a Jetpack ID, if present in the system, is guaranteed to be unforgeable. | Jetpacks are accessible through the <tt>jetpack:</tt> protocol. Each Jetpack has a keypair associated with it, and a Jetpack's ID is the SHA-1 hash of its public key. Jetpacks must be signed using their private key, and will not be loaded unless signed; thus a Jetpack ID, if present in the system, is guaranteed to be unforgeable. | ||
=== Use-Cases === | |||
* The wants to display an image/resource/L10n bundled with a Jetpack - option for allowing exposure of resource location needs consideration | |||
* Developer debugging ergonomics | |||
* Dynamically created, cache enabled, resources | |||
=== Key Issues === | === Key Issues === | ||