Open Bug 923575 Opened 11 years ago Updated 2 years ago

Make UA override update more scalable and robust

Categories

(Core :: Networking: HTTP, defect, P5)

All
Gonk (Firefox OS)
defect

Tracking

()

People

(Reporter: jchen, Unassigned)

References

Details

(Whiteboard: [necko-would-take])

From bug 897221, (In reply to Andreas Gal :gal from comment #35) > I would like to see a follow-up bug with a better scaling approach. UA > issues will be with us for a while. Even if we focus on the top N sites in > top K locales, we can easily grow a 50k list just to address the most urgent > UA issues. > > Scaling issues: > - we don't want to keep this in memory all the time (database in indexeddb > or even better a mmapped sorted list?) > - we don't want to re-download the whole list all the time (we should factor > out the download code into a generic incremental update-capable download > path for lists like this and others) > - we don't want to slow down network requests with the lookup (maybe add a > bloom filter that helps us preselect where to check for overrides at all) > - some devices don't care about UAs for some locales, so how about a per-TLD > list that is downloaded the first time you access that TLD? > > We don't need to address all of this at once, but lets have a clear plan. (In reply to Andreas Gal :gal from comment #36) > Last bit I forgot: bonus points if we can come up with a way to detect the > top N sites. This will need some solid privacy reviewing etc but it would > definitely help maintaining the UA override list. If we know the top N sites > people go to in a locale, we can do some analysis and see if we get the > right mobile content with the FFOS vs WebKit UA and then focus evangelism > and overrides as needed.
I think the two issues from the two comments are really two separate issues. I'd prefer to see a separate bug for the top sites suggestion as that is going to require privacy and legal review before we can proceed.
Whiteboard: [necko-would-take]
Priority: -- → P5
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.