- From: Sergio Garcia Murillo via GitHub <sysbot+gh@w3.org>
- Date: Sat, 26 Jan 2019 14:52:03 +0000
- To: public-webrtc-logs@w3.org
let's put it in a different view. Taking into account just one single datachannel will the proposed solution solve the issue? Also, does the problem about multichannel buffering still exist without taking into account the event loop queueing issue? you may have a solution for not problems simultaneously, but it also requires a change in w3c apis and ietf specs. To solve this issue we only need one line in the spec without api change. El sáb., 26 ene. 2019 14:52, Sergio Garcia Murillo < sergio.garcia.murillo@gmail.com> escribió: > your issue is a valid one but it's different than the current one even If > the solutions may be similar, that's why we propose you to open a > different issue to solve it. > > El sáb., 26 ene. 2019 14:41, Lennart Grahl <notifications@github.com> > escribió: > >> Then we're talking about the same thing. Please, explain where my example >> is incorrect. >> >> — >> You are receiving this because you were mentioned. >> Reply to this email directly, view it on GitHub >> <https://github.com/w3c/webrtc-pc/issues/2086#issuecomment-457832013>, >> or mute the thread >> <https://github.com/notifications/unsubscribe-auth/ABBW8x_SkPlj-lqTiPGggkqJIWbfKhwpks5vHFrwgaJpZM4aS7_J> >> . >> > -- GitHub Notification of comment by murillo128 Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2086#issuecomment-457837166 using your GitHub account
Received on Saturday, 26 January 2019 14:52:05 UTC