Seems like the right thing to do is to ship with whatever the current override list is at the build time and then update it dynamically.
-Brad On Jul 2, 2015 8:00 PM, "Ben Bucksch" <[email protected]> wrote: > Mike Taylor wrote on 02.07.2015 18:17: > >> I guess the first thing to do is figure out how we failed and go from >> there. In theory the gOverrideForHostCache is only cleared after a >> successful update fetch. >> >> < >> http://mxr.mozilla.org/mozilla-central/source/netwerk/protocol/http/UserAgentOverrides.jsm#54> >> >> >> (That does require us to trust that the server will work at least once >> when the user starts their first session. But I guess it's only broken >> twice in the past. ^_^) >> > > When I said "cache", I meant on disk, not in RAM. You should not request > the file on every startup, but only every 6-48 hours, maximum. > > Ben > _______________________________________________ > mobile-firefox-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/mobile-firefox-dev >
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
