465307 - Optimize network behavior in accordance with bearer

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, enhancement, P2)

Comment 1

[Patrick McManus [:mcmanus]]

 * would probably want to udpate the usual suspects: parallelism,
pipelining, proxy definitions and their auth tokens

 * would also want to close any persistent connections and flush the
dns cache on change of network

I'm pretty sure that can all be done dynamically in the existing
framework by shuffling prefs around.

Trickier is how to trigger that (i.e. how to identify change of network)
and how to configure it.

I can't think of anything portable to get that information. But there do
seem to be some platform specific answers.

Googling around a bit for platform based solutions, suggestor is probably
thinking of doing it with libconic which is in maemo:
http://maemo.org/api_refs/4.1/libconic-0.16/ 

It looks like windows can provide something too
http://msdn.microsoft.com/en-us/library/ms729302(VS.85).aspx

target n810 + maemo first

Comment 3

[Patrick McManus [:mcmanus]]

Attachment: Bearer Framework v1

This patch does the following -

* extend nsINetworkLinkService (2) to provide accessors for network name (often wifi name), and network type (mobile, wired, wlan, unknown). Observer notification made when any of those properties change.

* Implement new interface for Maemo via DBus
 
* create nsILinkBasedPrefs interface and implementation. Implementation links together default preferences with link-property contexts. Using this you can set different default preferences for different types of networks, or different network names. For instance "pref("network.linkpref.name.ducksong.misc.tree", false);" would set misc.tree to false if and only if the current network name was "ducksong". If the network name changed again misc.tree would be reset to its original value.

* Change the DNS implementation to note the change-in-link notification, and on receipt of this to clear its cache. This can help improve robustness in the case of mobile clients on split-DNS networks.

Comment 4

[Patrick McManus [:mcmanus]]

Attachment: mobile preferences using linked base pref patch

When the mobile device is known to be using a wired or wlan network, disable the pipelining default.

We might also want to use this infrastructure for other properties that are found to be latency sensitive - paint delay might be a candidate for that.

users may want to use this infrastructure for setting proxy preferneces - as you change networks the proxy settings can change automatically.

Comment 5

[Patrick McManus [:mcmanus]]

this is an old maemo bug .. b2g has better approaches now