Closed
Bug 512495
Opened 15 years ago
Closed 9 years ago
Expose method to XUL/Chrome to query connection type
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
RESOLVED
DUPLICATE
of bug 667980
People
(Reporter: blassey, Unassigned)
Details
Applications such as Fennec would like to be intelligent about how they use their user's data plans. For instance, choosing to download application updates when the user is connected by wifi versus cellular. Exposing a method to js to determine the type of connection would allow this behavior.
Comment 3•14 years ago
|
||
There's a DAP draft for this (http://dev.w3.org/2009/dap/netinfo/Overview.html). I guess we'll also want it to be exposed to chrome?
Comment 4•14 years ago
|
||
I do not think having 'connection.CELL_3G' makes any sense at all. f/e, i sit under the worse wifi hotspot in Mountain View. My phone would report that I have a "wifi" connection because that is the transport I am connecting over. However, if I switch over to 3g, I get higher throughput and less latency. Instead, we should have "some" way to tell the user what the average latency and average throughput has been over some period of time.
No longer blocks: 531874
Comment 5•14 years ago
|
||
(In reply to comment #4) > I do not think having 'connection.CELL_3G' makes any sense at all. f/e, i sit > under the worse wifi hotspot in Mountain View. My phone would report that I > have a "wifi" connection because that is the transport I am connecting over. > However, if I switch over to 3g, I get higher throughput and less latency. > > Instead, we should have "some" way to tell the user what the average latency > and average throughput has been over some period of time. Getting QoS metrics is fine, but getting the connection type is still a valid feature.
Comment 6•14 years ago
|
||
We probably also want an event listener to be notified when switching from a network to another.
Comment 7•14 years ago
|
||
mfinkle, i don't care what is exposed to xul/chrome, but exposing it to the web has larger consequence.
Comment 8•14 years ago
|
||
(In reply to comment #7) > mfinkle, i don't care what is exposed to xul/chrome, but exposing it to the web > has larger consequence. Agreed. To hell with web content. (In reply to comment #6) > We probably also want an event listener to be notified when switching from a > network to another. This bug is all about chrome. An Observer notifications would be perfect.
Updated•14 years ago
|
Summary: Expose method to query connection type → Expose method to XUL/Chrome to query connection type
Would bug 531874 be related to this issue?
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•