Sorry, should have been more clear. I wasn't suggesting we do this for
favicons (since, as you point out, we don't use necko). Instead I'm
suggesting we do this for anything else we're using necko for, like for
instance a blacklist request.
-Brad
On 1/14/14, 1:26 PM, Mark Finkle wrote:
This should not affect Firefox for Android the same as Desktop. We do
not use Gecko to fetch favicons. We use the Android networking stack.
That said, we could look at finding ways to reduce the priority of the
Android networking call, either with a handy-dandy API like the one
Gecko supports, or some other way, such as making sure we wait for the
Gecko pageload to complete before doing any Android networking.
------------------------------------------------------------------------
Jason Duel called out in the platform engineering meeting that we
have the ability (and should use it) to set priorities on
channels. Specifically he called out bug 802573, where loading
favicons was getting in the way of loading pages, but suggested it
be used anywhere where we're loading something over the network
that the user isn't specifically waiting for.
Code for setting it looks like this:
priorityChannel->AdjustPriority(nsISupportsPriority::PRIORITY_LOWEST);
where priorityChannel is an instance of nsISupportsPriority.
-Brad
_______________________________________________
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
