- From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
- Date: Tue, 6 Jan 2015 13:32:51 +0100
- To: Harald Alvestrand <harald@alvestrand.no>
- Cc: Singh Varun <varun.singh@aalto.fi>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On 06 Jan 2015, at 07:13, Harald Alvestrand <harald@alvestrand.no> wrote:
> Den 06. jan. 2015 00:14, skrev Singh Varun:
>> Hi Harald,
>>
>> Response inline.
>>
>>> On 05 Jan 2015, at 23:40, Harald Alvestrand <harald@alvestrand.no> wrote:
>>>
>>> The current RTCStatsType is defined like this:
>>>
>>> enum RTCStatsType {
>>> "inboundrtp",
>>> "outboundrtp",
>>> "session",
>>> "track",
>>> "transport",
>>> "candidatepair",
>>> "localcandidate",
>>> "remotecandidate"
>>> };
>>>
>>> There are no values for the datachannel stats.
>>>
>>> To make this symmetric with RTP, I suggest we add "inbounddata" and "outbounddata".
>>>
>> I presume that the stats currently in RTCDataChannelStats will then be split to inbound and outbound?
>
>
> On second consideration, that doesn't make sense. The reason RTP is
> split is that RTP is unidirectional, while datachannel is bidirectional.
>
> Second proposal:
> The string should be "datachannel". No split.
Are there counters needed for abandoned messages? Should these counters
be different for messages which have never been sent or for which at least
one part was sent once?
Best regards
Michael
>
>
>>
>> dictionary RTCDataChannelStats : RTCStats {
>> DOMString label;
>> DOMString protocol;
>> long datachannelid;
>> RTCDataChannelState state;
>> };
>>
>> dictionary ourbounddata: RTCDataChannelStats {
>> unsigned long messagesSent;
>> unsigned long long bytesSent;
>> }
>>
>> dictionary inbounddata: RTCDataChannelStats {
>> unsigned long messagesReceived;
>> unsigned long long bytesReceived;
>> }
>>
>> —
>> http://www.netlab.tkk.fi/~varun
>>
>
>
>
Received on Tuesday, 6 January 2015 12:33:20 UTC