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

Re: Data API Proposal aligned to WebSocket

From: Adam Bergkvist <adam.bergkvist@ericsson.com>
Date: Thu, 23 Feb 2012 14:27:10 +0100
Message-ID: <4F463EAE.70309@ericsson.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
On 02/23/2012 02:08 PM, Michael Tuexen wrote:
>
> On Feb 23, 2012, at 1:39 PM, Adam Bergkvist wrote:
>> You're right that it's not used in either of the examples given here. It's a pure API-related property to help the developer identify a particular DataChannel object if several objects (with the same transport porperties) are used. E.g. you might have a DataChannel object with label "chat" and another with the label "game-data" for different purposes.
> OK. So if I understand this correctly, it is just a local thing and it is not expected to be on the wire, right?

Yes, it's not intended to be some "channel id" on the wire, but
it would have to be transported to the other end so that the 
corresponding DataChannel object on the B-side can be initialized with 
the same label.

>>> What about unordered? When do you expect a message to be abondoned when treated unreliable?
>>
>> I don't really have an opinion on when to abandon messages in unreliable mode.
> OK. But it needs to be specified.

True.

/Adam
Received on Thursday, 23 February 2012 13:32:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 23 February 2012 13:32:53 GMT