- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 May 2024 17:11:30 +0000
- To: public-webrtc-logs@w3.org
Tentative evaluation of pros and cons: Pros for transferable approach - Potential ability to move objects from one worker to another one, flexibility Cons for transferable approach - API is not worker first but worker second - Transferring complex objects is difficult - Need to define how transfer works (what happens to events that are about to be fired for instance) - Need to define how a transferred object behaves - Need to define when object may or may not be transferred Pros for non transferable approach - API is worker first - Simpler specification and implementation Cons for non transferable approach - Less flexible, requires the web application to make processing choices at setup time -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/issues/36#issuecomment-2110734617 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 14 May 2024 17:11:31 UTC