Re: [webrtc-rtptransport] Should RtpSendStream/RtpReceiveStream be transferable? (#36)

Pros for the transferable approach:
- Allows API users to decide on allocation of tasks to threads
Cons for the one-off approach:
- Doesn't permit applications that make their own decisions on where to allocate tasks to threads

We have already tackled many of the transferable-approach issues when dealing with transfer of tracks.
There's no such thing as a "self-explanatory" API. There is just more or less explanation needed.


-- 
GitHub Notification of comment by alvestrand
Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/issues/36#issuecomment-2114879605 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 16 May 2024 10:48:51 UTC