Closed
Bug 764201
Opened 13 years ago
Closed 13 years ago
Need the ability to remap assets that are stored in the appcache
Categories
(Firefox OS Graveyard :: General, defect)
Firefox OS Graveyard
General
Tracking
(blocking-basecamp:-)
RESOLVED
WONTFIX
| blocking-basecamp | - |
People
(Reporter: ladamski, Unassigned)
Details
For apps that are hosted by the app store, we need the ability to remap their origin from the marketplace to their original when/after we add them to the app cache.
1) Scenario store is hosting an app that is "homed" in https://myapp.com/coolapp
2) Marketplace downloads app from https://myapp.com/coolapp/v1, reviews and approves it, and hosts it on https://coolapp.marketplace-apps.org
3) At installation time, the client downloads the assets from https://coolapp.marketplace-apps.org, but needs them to behave as though their location is under https://myapp.com/coolapp
This means we need to be able to override the origin store for each asset in an appcache.
| Reporter | ||
Updated•13 years ago
|
Blocks: b2g-updates
| Reporter | ||
Updated•13 years ago
|
Summary: Need the ability to remap assets that are store in the app cache for store hosted apps → Need the ability to remap assets that are stored in the appcache
Comment 1•13 years ago
|
||
Would that app be updated from the app store or from its 'home' site?
| Reporter | ||
Comment 2•13 years ago
|
||
Potentially either. This makes it possible to update an app from anywhere (so long as its authenticated) without requiring the app to be aware of that.
Comment 3•13 years ago
|
||
This blocks bug 764194 which in turn blocks bug 764189 which Lucas has nominated as a basecamp blocker so I'm nominating this, too.
Updated•13 years ago
|
blocking-basecamp: --- → ?
I think this is WONTFIX. We should instead implement the app:// protocol which won't use the appcache at all
blocking-basecamp: ? → -
Comment 5•13 years ago
|
||
app protocol? that's new to me. Is there any bug or document that describes what it is intended to be implemented?
You need to log in
before you can comment on or make changes to this bug.
Description
•