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

Re: Should we get drop RTCAnswerOptions?

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Sun, 14 Feb 2016 17:17:22 +0000
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B37492D4A@ESESSMB209.ericsson.se>
Thanks Cullen. I had already closed the Issue as "won't fix" as no one 
said we should make the change. Now we even got one person saying we 
should not change!

On 14/02/16 18:10, Cullen Jennings (fluffy) wrote:
>
> I think having the two types reduces the options for mistakes and might be important in the future. I'd say leave as it is. It's not like changing it makes anything easier.
>
>
>> On Jan 19, 2016, at 11:12 AM, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> wrote:
>>
>> Hi,
>>
>> referring to Issue #330 [1] which rightfully points out that
>> RTCAnswerOptions is just a copy of RTCOfferAnswerOptions, and the latter
>> could be used directly as argument to createAnswer.
>>
>> Is this a change we should do, or is there a chance we may want to add
>> Answer specific things to RTCAnswerOptions?
>>
>> Stefan
>>
>>
>>
>> [1] https://github.com/w3c/webrtc-pc/issues/330
>>
>
>
Received on Sunday, 14 February 2016 17:17:56 UTC

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