WebAPI/NetworkAPI: Difference between revisions
< WebAPI
Jump to navigation
Jump to search
(→Proposed API: float -> double) |
|||
| Line 16: | Line 16: | ||
== Proposed API == | == Proposed API == | ||
partial interface Navigator { | |||
readonly attribute Connection connection; | readonly attribute Connection connection; | ||
}; | }; | ||
interface Connection | interface Connection | ||
{ | { | ||
Revision as of 22:49, 1 December 2011
Device API specification
The DAP WG (W3C) has specification sharing this proposal goal [1]. Our proposal might or might not look like it for the moment. Suggestions and comments will be submitted to the Device Status Task Force [2].
[1] http://dev.w3.org/2009/dap/netinfo/ [2] http://lists.w3.org/Archives/Public/public-device-status/
Status
The proposed specification doesn't have a working implementation yet. The implementation will be done in {bug|677166}.
Demo
TBD
Proposed API
partial interface Navigator {
readonly attribute Connection connection;
};
interface Connection
{
// Estimated speed (in MB/s) of the current connection.
readonly attribute double speed;
// Return whether the current connection is restricted (like quota, pay per use, etc.).
readonly attribute boolean restricted;
}
Notes
- .speed will be some arbitrary values for the moment. It might be really estimated later.
- .restricted is going to return false unless a pref is switched by the user. In that case, it will return true if the connection is of a mobile type (like 2/3/4g).
- There is no .type because we believe that might be abused. It could be added later if there is a strong need for it.