Confirmed users
587
edits
User:Clouserw/AMO/Perf: Difference between revisions
Jump to navigation
Jump to search
→Open Questions
| Line 63: | Line 63: | ||
* (An add-on can have many versions which can have many files) AMO for the most part advertises versions to the end user and figures out what file to serve (often only differing in OS) automatically. Would it be more appropriate to associate performance data with add-on versions rather than files? | * (An add-on can have many versions which can have many files) AMO for the most part advertises versions to the end user and figures out what file to serve (often only differing in OS) automatically. Would it be more appropriate to associate performance data with add-on versions rather than files? | ||
** Yes, that seems fine. The Add-ons Manager can't currently differentiate between different XPIs anyway (except via source URL, which isn't always available). AFAICT, AMO only lets XPIs differ by what OS they support - and that's handled fine by a generic per-version form. | |||
* A similar question for add-ons not hosted at AMO. Associating with GUID+Version sounds like the right thing to do there anyway. | * A similar question for add-ons not hosted at AMO. Associating with GUID+Version sounds like the right thing to do there anyway. | ||
** Yep. Anything more complex (eg, hashing the XPI) seems overkill for this. | |||
* How this works for add-ons not hosted at AMO is ignored in the steps above still. | * How this works for add-ons not hosted at AMO is ignored in the steps above still. | ||