W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2014

Re: asynchrony for addStream w/ error/success callbacks

From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 10 Jan 2014 15:22:41 -0800
Message-ID: <CABcZeBMxg4kZzdFt9n5h5JwH9JBVe9C0mDQ2Hf0qoZYfO=eA9A@mail.gmail.com>
To: Jan-Ivar Bruaroey <jib@mozilla.com>
Cc: Adam Roach <adam@nostrum.com>, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>, Martin Thomson <martin.thomson@gmail.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On Fri, Jan 10, 2014 at 3:16 PM, Jan-Ivar Bruaroey <jib@mozilla.com> wrote:
> On 1/10/14 5:07 PM, Adam Roach wrote:
>>
>> On 1/10/14 12:03, Jan-Ivar Bruaroey wrote:
>>>
>>> The createOffer error callback. It's an add/remove cart and checkout
>>> pattern.
>>
>>
>> On every e-commerce site I've ever used, an attempt to add an out-of-stock
>> item (or more of an item than they have in stock) will complain at that very
>> moment, as opposed to waiting for an attempt to checkout.
>
>
> You have the item already, so you know you're not sold out. You don't learn
> that when you add.
>
> But it appears my analogy is not helping. Have you ever filled in a
> C-language struct or JS object and passed that to a call? Same thing.

Except, you know, that it's not, since we're making a series of
independent subroutine calls and the API has an opportunity to
detect that it's not going to work, it just declines to tell us.

-Ekr
Received on Friday, 10 January 2014 23:23:50 UTC

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