W3C home > Mailing lists > Public > public-device-apis@w3.org > April 2011

Re: ACTION-357: Network Connection API draft

From: Rich Tibbett <richt@opera.com>
Date: Wed, 06 Apr 2011 16:58:46 +0200
Message-ID: <4D9C7FA6.5040504@opera.com>
To: Suresh Chitturi <schitturi@rim.com>
CC: public-device-apis@w3.org
Hi Suresh,

It might also be good to define a NetworkChangeEvent that allows a web 
app to be notified whenever the current connection type changes.

Something as follows:

interface NetworkChangeEvent : Event {
     readonly attribute unsigned short        type;
     void initBatteryStatusEvent (in DOMString type, in boolean bubbles, 
in boolean cancelable, in unsigned short type);

If an event listener is registered with the event type 'networkchange', 
then the User Agent MUST dispatch a NetworkChangeEvent event 
immediately. User Agents SHOULD dispatch a NetworkChangeEvent event 
whenever the connection type changes.

There should be no issues regarding the Security and Privacy 
considerations with the interfaces currently in the spec and above. Did 
you have any thoughts on what you wanted to include in that section?

- Rich

Suresh Chitturi wrote:
> 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.
Received on Wednesday, 6 April 2011 14:59:21 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:48 UTC