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. Thanks, Rob _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
