- From: Kiran Kumar <g.kiranreddy4u@gmail.com>
- Date: Mon, 3 Mar 2014 12:18:54 +0530
- To: Harald Alvestrand <harald@alvestrand.no>
- Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
Received on Monday, 3 March 2014 06:49:41 UTC
Hi Harald, Thank you for your response. Actually, I missed the oniceconnectionstatechange while providing above example, which will be covered by existing callbacks. But AFAIK, single call-back to all the notifications which can distinguish with a notification type enum or string, will be more useful for extending the notifications in future. Thanks, Kiran. On Fri, Feb 28, 2014 at 5:14 PM, Harald Alvestrand <harald@alvestrand.no>wrote: > On 02/27/2014 05:46 AM, Kiran Kumar wrote: > > Dear All, > > I would like to propose a NotificationCallback for RTCPeerConnection > > object. > > This is useful, for example, in following conditions. > > before doing so, it would be good to have your comments on the existing > notification callbacks, of which there are several. > > > > 1. If connection is not established between the two peers within a > > specified time frame, then platform can convey the userAget regarding > > the connection state. > > oniceconnectionstatechange? (checking -> failed, I think) > > > > 2. If connection state is expired in the middle of the session. > > etc. > > oniceconnectionstatechange? (connected -> disconnected) > > > > > Suggestions and Feedback welcome. > > > > Thanks, > > Kiran. > > > -- > Surveillance is pervasive. Go Dark. > > >
Received on Monday, 3 March 2014 06:49:41 UTC