On 06/09/2014 10:26 AM, Red wrote: > Do you agree with the idea of having the "update" object become an array > of objects with the update's respective information? It will add some > complexity to the way the update information is parsed (albeit not much) > and probably save a great deal of trouble in configuring preferences > with releases.
Why an array instead of key-value pairs keyed by "stable", "development", etc? One advantage of separating the URL paths for development vs stable is that we get marginally better statistics on how many users are pinging for stable vs. development ruleset updates, which can sometimes be useful for debugging. But perhaps this is too marginal. :) What trouble does this save in configuring preferences? I'm not sure I follow. -Yan
signature.asc
Description: OpenPGP digital signature
_______________________________________________ HTTPS-Everywhere mailing list [email protected] https://lists.eff.org/mailman/listinfo/https-everywhere
