- From: Thomas Guilbert via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Aug 2024 21:17:12 +0000
- To: public-webrtc-logs@w3.org
> [...] but I suspect that we will have more difficulty for datachannels that are not within an agent cluster. Indeed, supporting `DedicatedWorkers` was a low hanging fruit, whereas supporting `ServiceWorkers` would require some serious re-architecturing, and we can't commit to supporting it at this moment. As a side note: a `peerconnection` is not transferrable and [closes](https://w3c.github.io/webrtc-pc/#operation:~:text=Set%20the%20%5B%5BReadyState%5D%5D%20slot%20of%20each%20of%20connection%27s%20RTCDataChannels%20to%20%22closed%22.) all of its `RTCDataChannels` when it closes. Does this limit the usefulness of transferring `RTCDataChannels` to `ServiceWorker`, since their lifetime is still tied to the `Window` that originated them? Integrating `DedicatedWorker` only for now sounds like a good plan. -- GitHub Notification of comment by tguilbert-google Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2986#issuecomment-2297472785 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 19 August 2024 21:17:13 UTC