- From: Tony Herre via GitHub <sysbot+gh@w3.org>
- Date: Thu, 20 Jun 2024 13:57:27 +0000
- To: public-webrtc-logs@w3.org
> I think we should keep the new example from #42 and the updated example from #51 (with the event payloads removed). I'm fine with either naming scheme. Done, I think. Adopted the naming scheme from #51. Also removed the comment and examples which had data in the events themselves. > We can deal with the "is the max number optional?" either in this PR or in a separate one I wasn't sure which way to go with this - what's the default if the app doesn't provide a max, it just gets the entire queue of many (thousands?) of packets in one chunk? Forcing the JS to specify some number feels like it might be good for avoiding surprises and doesn't add too much complexity, or? Don't feel that strongly though, so happy to add it and discuss removing it in an issue or meeting etc. PTAL all! -- GitHub Notification of comment by tonyherre Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/pull/42#issuecomment-2180777325 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 20 June 2024 13:57:28 UTC