777658 - Provide way for necko channels w/o callbacks to be limited (or not) to wifi-only connections

Status: NEW

(Core :: General, defect)

Description

[Jason Duell]

My understanding is that some necko clients don't have regular callbacks (i.e. they're null, or don't GetInterface to nsILoadContext).  IIRC examples include chrome loads like checking for updates, getting updated phishing lists from google, etc.  (Does anyone know offhand of other use cases here?  I haven't had time to grep for them yet).

In B2G we still want to be able to 1) meter how much these loads take (possibly under different classifications) and 2) limit them to wifi-only connections or not.   This will vary on what the load is used for (may want to limit upgrades while still allowing phishing updates, etc).

The most obvious way to achieve this that I can think of is to reserve some appIds for the various tasks here, and then change the call sites to arrange that they provide callbacks that implement nsILoadContext and return the given AppId.  We can provide utility functions that handle the grunge work here if needed.