Network Connection API draft (update)

Hi all,

 

Attached a minor update to the Network API draft, based on the
discussions so far.

 

Change Log:

 

-          Change const NONE to '20' for future proofing reasons

-          Added support for 'roaming'. As opposed to having an
attribute "roaming" (which can be tricky in some situation where the
operators are present in multiple regions and the accuracy of this
information from the device) I have introduced the two attributes
"homeNW" and "currentNW" which can be used to derive whether the device
is in roaming or not e.g. if homeNW != currentNW it can be inferred as
roaming. 

 

The only change that is pending is the "network change" event. In the
last call we discussed about the possibility to use online for
indicating network change. Reading the use of online event I don't think
it is appropriate and would prefer to create our own event. Rationale:
The semantics of online event is different from a network change (online
is only used to indicate whether the user is connected to the network
and is "online" i.e. has internet access).

 

However, I think we should adopt the same approach used with online
event when it comes to the model i.e. define a 'networkchange' event
handler IDL attribute on the Window object fire a simple event (
http://dev.w3.org/html5/spec/webappapis.html#fire-a-simple-event) on the
Window object, it is a light weight approach and does not require the
overhead of defining a new NetworkChangeEvent interface and the model
(bubbling, etc.) that comes with it.

 

If this works I can go ahead and incorporate it.

 

Regards,

Suresh

PS: I will be travelling next week, and unsure if I will be able to join
the call but please feel free to discuss this update.

 

 

From: public-device-apis-request@w3.org
[mailto:public-device-apis-request@w3.org] On Behalf Of Suresh Chitturi
Sent: Friday, March 25, 2011 1:47 PM
To: public-device-apis@w3.org
Subject: ACTION-357: Network Connection API draft

 

Hi all,

 

As per my ACTION-357, please find attached a draft spec for Network Info
API.

As discussed during the F2F, the proposed draft is just a formalization
of the proposal from [1] with minor changes.

 

Let me know if you have any comments, before we begin to advance this
further.

 

[1] 
http://lists.w3.org/Archives/Public/public-device-apis/2010Oct/0076.html

 

Regards,

Suresh

PS: I am yet to set up my cvs account, and therefore not able to
check-in to cvs.

--------------------------------------------------------------------- 
This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client or other applicable privileges), or constitute
non-public information. Any use of this information by anyone other than
the intended recipient is prohibited. If you have received this
transmission in error, please immediately reply to the sender and delete
this information from your system. Use, dissemination, distribution, or
reproduction of this transmission by unintended recipients is not
authorized and may be unlawful. 


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.