Conversation
This helps set the background for API change proposals.
youennf
left a comment
youennf
left a comment
There was a problem hiding this comment.
Thanks for writing this explainer, this is helpful to drive the discussion forward.
At this stage of the discussion, I think we should dive further into use cases to extract technical requirements we could put on existing APIs (or identify missing new APIs).
This would also allow adding these technical requirements in this document and link them to NV use cases.
|
|
||
| In some use cases, we need to move encoded data beyond the confines of a single PeerConnection. | ||
|
|
||
| The use cases include: |
There was a problem hiding this comment.
Below use cases are closer to technical solutions than actual use cases.
It would be helpful to relate these technical solutions to NV document use cases.
There was a problem hiding this comment.
I have filed w3c/webrtc-nv-use-cases#81 and w3c/webrtc-nv-use-cases#82 in order to provide a discussion point for those use cases, before spending the time to write actual text for the use case.
w3c/webrtc-nv-use-cases#79 has been merged, so that's part of the NV-use-cases now.
Case fix Co-authored-by: Philipp Hancke <phancke@microsoft.com>
|
This issue was mentioned in WEBRTCWG-2023-01-17 (Page 30) |
4 participants
This helps set the background for API change proposals.