- From: Cullen Jennings (fluffy) <fluffy@cisco.com>
- Date: Mon, 17 Sep 2012 20:58:39 +0000
- To: Justin Uberti <juberti@google.com>
- CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
Two suggestions to this 1) add an enum that reports state of gathering 2) add an enum that reports state of checking then merge starting and checking since they both the same sate with respect to the JS app with the only difference being that setRemote has been called. It's weird to have the only thing that can change the sate is a call from the app that will immediate result in a callback to app and there is nothing else that would cause this state transition On Sep 10, 2012, at 12:26 AM, Justin Uberti <juberti@google.com> wrote: > I updated my IceState proposal (which corresponds to Option A, or the high-level part of Option C) based on the points raised at Thursday's discussions. Please take a look at the "IceState proposal" section in the attached document, and let me know what you think. > > > On Thu, Sep 6, 2012 at 7:55 AM, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote: > > Updated slides with Justin Option C added .. > > > <WebRTCstatesandcallbacks.pdf>
Received on Monday, 17 September 2012 20:59:08 UTC