Re: [webrtc-extensions] Investigate the possibility to interact with data channel in workers (#64)

Right, we have a few options:
1. Transfer a data channel at creation time: easy non-main-thread blocking implementation, ensure all events can be dispatched to the application.
2. Transfer a data channel if app is not listening and not writing: easy non-main-thread blocking implementation, some events can be lost but app does not seem to care since it is not listening.
3. Transfer a data channel whatever the state while ensuring proper event dispatching and ordering: easy implementation if we rely on main thread to do the synchronisation, but we probably do not want that. More difficult implementation otherwise.

WebKit prototype is doing 1.
It might be good to get feedback on how much 2 would be more appealing.
From the feedback I received so far, 3 does not seem worth the effort.

-- 
GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/64#issuecomment-800074185 using your GitHub account


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

Received on Tuesday, 16 March 2021 08:50:57 UTC