- From: Jimmy Wärting via GitHub <noreply@w3.org>
- Date: Thu, 23 Jul 2026 10:15:16 +0000
- To: public-webrtc-logs@w3.org
> > [@molvqingtai](https://github.com/molvqingtai) what use case do you have where transferring a RTCPeerConnection to a Worker doesn't work? > > Transferring isn't the problem I'm trying to solve. I'm interested in a SharedWorker owning a single `RTCPeerConnection` so multiple pages can share it and page reloads don't require reconnecting. Dito, I also want to remain connected to a single connection (shared across all tabs) and also durning page reload (without having to build a SPA) Being able to establish a p2p connection on a SharedWorker, without transferring a `DataChannel`, would be very useful. When a page reload, then the `RTCPeerConnection` closes, and so dose the transfered `DataChannel` along with it. -- GitHub Notification of comment by jimmywarting Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/230#issuecomment-5057240287 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 23 July 2026 10:15:17 UTC