On Mon, Sep 10, 2012 at 10:25 AM, Rob Hudson <[email protected]> wrote: > Hi All, > > I've been working on adding packaged app support to the Marketplace. So far > I've been using AMO as the "spec" but thought I'd bring up how AMO handles > disabled apps and deleted versions as it may impact the update service and > also Firefox OS. > > Disabled by User: > > AMO allows the developer to disable and re-enable their add-on at any time. > This removes it from any of our queries so it no longer appears in searches > or other public listings. When the add-on is disabled by the user, it also > removes it from the update service and returns an empty RDF document. I bring > this up since we allow the same on Marketplace at the moment and this case > should be taken into consideration as we develop the update service. I'm also > curious how Firefox OS will deal with this case but would assume similar to > Firefox, which will continue to allow the add-on to work locally but it will > stop receiving updates until the developer re-enables it. > > Version Deletion: > > AMO allows the developer to delete a version at any time, regardless of > approval status. The reasoning behind this I've heard is to keep the > developer in full control of their code and add-ons. When the developer > deletes a version this also deletes the associated files with that version > and also the associated reviews with that version. The update service would > start returning the prior approved version in this case -- e.g. if versions > 1.0 and 1.1 existed before and the developer deletes version 1.1, the update > service would return version 1.0. I'm told that Firefox refuses to downgrade > add-ons to a lesser version. > > I haven't yet coded version deletion for Marketplace yet, but am working on > it this week. If it is developed the same as AMO I think the above case is > important to take into consideration as we develop the update service and > test on Firefox OS. If this should change in any way, please let me know.
We don't have "support" for either of these things on the device side in Firefox OS right now. Generally speaking we are only planning on allowing users to download the latest version, so the developer deleting or disabling an older version should have no effect. In fact, I'd recommend that we automatically treat approval of a new version as a removal of any older versions from the store. As for the author deleting or disabling the latest version, my gut instinct is to allow the user to keep running whatever they have installed. Would that be ok? Though it would be great if we had support for handling the situation when bad security problems are found in an app such that we can block it. This either at request of the author, or due to us finding out about this. Unfortunately it's unlikely that we'll have time to implement true blocklisting of apps in v1. The best thing we've been able to come up with for v1 is here: https://bugzilla.mozilla.org/show_bug.cgi?id=773117#c1 / Jonas _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
