W3C home > Mailing lists > Public > public-webrtc@w3.org > December 2015

Re: Issue 440: Use interfaces not dictionaries

From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 18 Dec 2015 11:28:43 +1100
Message-ID: <CABkgnnWztSqfmAvpQLz1LsMbXnWw4kASjr2jETeyaY6QsSbo=w@mail.gmail.com>
To: Bernard Aboba <Bernard.Aboba@microsoft.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On 18 December 2015 at 02:05, Bernard Aboba <Bernard.Aboba@microsoft.com> wrote:
> [BA] Except that the set of read-only attributes can and will change
> dramatically with WebRTC NV – and we will then need to make dramatic changes
> to the API which might not have otherwise been necessary.

That's just suggesting that we hide changes by using a dictionary.

> [BA] When a method returns a dictionary, that dictionary is automatically
> read-only, because changing attributes in it only affect the local copy.

Sort of.  It's really more akin to throwing data over the fence
without regard for its welfare.

> When you change a method or create a new one that now requires some of the
> information returned in another method, the interface concept becomes an
> albatross, because at that point you need *both* the interface and a new
> dictionary including the same attributes!

Let me check the priority of constituencies again...
Received on Friday, 18 December 2015 00:29:12 UTC

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