W3C home > Mailing lists > Public > public-webrtc@w3.org > February 2012

Data API: what is agreed, what is open

From: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>
Date: Tue, 7 Feb 2012 18:10:10 +0100
Message-ID: <4F315AF2.1000403@ericsson.com>
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Hi all,

trying to summarize the discussion on the Data API, I come to this:

* The API should allow for the application to use multiple channels
(without having to to do muxing in the app)
* The API should allow the application to select reliable or unreliable
transmission (where "reliable" also means "in order delivery")
* The API should initially enable sending and receiving DOMString, Blob
and ArrayBuffer data
* The API should allow the application to check if data is being
buffered (so that it can adjust the send rate)
* The API should be designed to allow extension in functionality (e.g.
set priority, set that in-order delivery is not to be used for reliable,
etc.) and data types (e.g. to introduce Stream once the WebApps WG
defines it)

* Should the API be uni- or bi-directional?
* Should there be a specific "open" signal to the application (or should
the object dealt with when sending only be made available when
transmission is possible), or should data be buffered until it can be
transmitted (i.e. the app can always "send")?

We would like comments, both if you agree to what we state as "agreed", 
and input on what you prefer on the open issues. And of course other 
things we have a agreement on, and other things that are open.

Stefan for the chairs
Received on Tuesday, 7 February 2012 17:13:49 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:27 UTC