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

RE: ACTION-357: Network Connection API draft

From: Niklas Widell <niklas.widell@ericsson.com>
Date: Wed, 30 Mar 2011 10:26:09 +0200
To: "Tran, Dzung D" <dzung.d.tran@intel.com>, Suresh Chitturi <schitturi@rim.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <6FFCEF6A0AE1D6468ADD4281840995621EC44442D6@ESESSCMS0352.eemea.ericsson.se>
I think we should limit ourselves to an API that returns the connection type being used by the web app, perhaps (big perhaps) also network name (APN, SSID, etc) but nothing else.

Allowing apps to manage their own connection will increase implementation complexity, put a heavy requirement on the developer to make things work in possible edge case scenarios as well as open a can of worms security wise.

(footnote: for limited/"curated" environments it might be ok for a web app to handle it's own connection type, but then it would be a proprietary extension in that environment)

Best regards,
Niklas
________________________________
From: public-device-apis-request@w3.org [mailto:public-device-apis-request@w3.org] On Behalf Of Tran, Dzung D
Sent: den 30 mars 2011 01:00
To: Suresh Chitturi; public-device-apis@w3.org
Subject: RE: ACTION-357: Network Connection API draft

For instance a web app  can determine that it has 3G and WiFi-direct peer to peer connection to the TV. It then can stream Youtube via 3G to the TV display.  Maybe for this release we don't want to support such use cases.

Thanks
Dzung

From: Suresh Chitturi [mailto:schitturi@rim.com]
Sent: Tuesday, March 29, 2011 3:34 PM
To: Tran, Dzung D; public-device-apis@w3.org
Subject: RE: ACTION-357: Network Connection API draft

Thanks for the use cases, but the question is do you see the Web App working simultaneously with both connections? For e.g. will the app work with two open connections in parallel or use one connection at a time regardless of the number of active connections. If it is the later my feeling is that the current API suffices because we say use the term 'current' connection which means the Web App can always get the handle to the current connection.

Regards,
Suresh

From: Tran, Dzung D [mailto:dzung.d.tran@intel.com]
Sent: Tuesday, March 29, 2011 10:15 AM
To: Suresh Chitturi; public-device-apis@w3.org
Subject: RE: ACTION-357: Network Connection API draft

Hello,

There are a couple of use cases that I can think of which are:

1)      Tethering: Using your WiFi for SoftAP and 3G as your data connection

2)      WiFi-direct: Using your 3G for your data connection while doing peer to peer over WiFi to another device.  WiFi-direct is coming as in the following spec: http://www.wi-fi.org/Wi-Fi_Direct.php



Thanks

Dzung

From: Suresh Chitturi [mailto:schitturi@rim.com]
Sent: Monday, March 28, 2011 3:28 PM
To: Tran, Dzung D; public-device-apis@w3.org
Subject: RE: ACTION-357: Network Connection API draft

Hi Dzung,

Thanks for your feedback.
You are right, this API only supports one connection. I have been thinking about the usefulness of multiple connections but in practice isn't it that the developer/user would only be interested in the 'current' connection type that is being used by the application as opposed to knowing that multiple connections exist e.g. "what is my current connection type"? If you are saying that multiple connections would be used simultaneously by the same web app then it makes sense to consider this in the API.

Regards,
Suresh

From: Tran, Dzung D [mailto:dzung.d.tran@intel.com]
Sent: Monday, March 28, 2011 10:37 AM
To: Suresh Chitturi; public-device-apis@w3.org
Subject: RE: ACTION-357: Network Connection API draft

Suresh,

>From this API, basically there is just Connection Type and it is up to the user to determine connection speed from the type. This seems reasonable enough, beside in some cases I think you might get multiple connections such as 3G and WiFi or Ethernet simultaneously.

Thanks
Dzung Tran

From: public-device-apis-request@w3.org [mailto:public-device-apis-request@w3.org] On Behalf Of Suresh Chitturi
Sent: Friday, March 25, 2011 11:47 AM
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.
---------------------------------------------------------------------
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, 30 March 2011 08:26:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:18 GMT