- From: Lennart Grahl via GitHub <sysbot+gh@w3.org>
- Date: Fri, 25 May 2018 20:46:49 +0000
- To: public-webrtc-logs@w3.org
We could of course also buffer the data but that will add some complexity: There would have to be some timer running that discards the messages and closes the data channel once it fires. So, basically I see the following solutions: When receiving a message on an unassigned stream ID... 1. discard it. Breaks the reliability promise. 2. run the closing procedure (reset incoming/outgoing stream). An easy fix but will not fix the problem with `createDataChannel` being useless after the connection has been established, since both would have to synchronise the opening or it would be a race. 3. buffer the messages for X seconds. If a negotiated channel has been created with the same ID, deliver the messages. Once the timeout fires, run the closing procedure. As mentioned, this will not be trivial to implement but would be the most satisfactory solution. We only have to determine *X*. :slightly_smiling_face: -- GitHub Notification of comment by lgrahl Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1879#issuecomment-392181452 using your GitHub account
Received on Friday, 25 May 2018 20:46:52 UTC