Bug 1180092 will implement user controlled cache-pinning for signed packages. We need to connect this to gaia's implementation of pinning. (somehow we need to make gecko aware of the gaia pinning concept).

I assume the control flow here is in the gaia->cache direction? I.e. gaia pinning tells the cache when & what to pin (and also when to unpin)?

(In reply to Jason Duell [:jduell] (needinfo? me) from comment #1) > I assume the control flow here is in the gaia->cache direction? I.e. gaia > pinning tells the cache when & what to pin (and also when to unpin)? Correct. At the moment the exact API is still being defined. Pinning is implemented in Gaia, but we will need some API to make Gecko aware of this. Fabrice has a work in progress patch in bug 1178536, which uses a customEvent sent from the system app to shell.js to facilitate this, so that might be what we use. Or maybe we will need to create a DOM api for this purpose. But either way you are correct, gaia will tell gecko when something is pinned and unpinned.

Once we have the API for HTTP cache pinning (bug 1032254), someone who knows gaia pinning should take this and call that API as needed.

Do we have someone to work on this? I'd throw someone from necko at it but the usual suspects are busy and AFAICT this is best done by someone who knows gaia pinning. I know bug 1032254 isn't done yet but the API there is simple enough (nsICacheEntry.pin = true) and unlikely to change, so we can probably move this along simultaneously.

I take it back--looks like we need bug 1180092 for this, not just 1032254.

Just to clear up dependencies here: 1. A signal from Gaia that the user is "Pinning" the content (this is a new FxOS concept akin to bookmarking). We need this same signal in gecko for registering web activities, and this is being implemented in bug 1178536 2. Once gecko recieve the signal that a package has been pinned, we need to change it's update behavior. That's 1180092 afaik. And Bug 1032254 is required for 1180092. So I'm assuming this bug will be fairly simple, just triggering whatever we implement in 1180092. Stephanie is already assigned to 1178536, so I think she is the best person to work on this bug.

This is not a 2.5 blocker since n-sec is not part of 2.5

Stephanie, Any update on this bug? Its a necessary bug to land for TV. Thanks

Hi Mahendra, I'm currently working on this as part of the new security model. Why is this necessary for TV and what is the deadline for landing this? Note it has several dependencies. Thanks

Josh, Can you please help with this information on why its required for TV?

Per comment 9, this bug is only for new security model, it is not required for TV in 2.5 scope.