- From: <piranna@gmail.com>
- Date: Sun, 24 Feb 2013 02:49:40 +0100
- To: discuss-webrtc@googlegroups.com, public-webrtc <public-webrtc@w3.org>
I've got this issue on Chrome v24 and v26, but I think it's related with the specificacion since I didn't see anything about it there. I'm trying to create a PeerConnection (to later create a DataChannel from it) from inside a WebWorker, with the idea of use in the future a SharedWorker. My intention is to move all the logic of my application (a P2P filesharing application) to a SharedWorker and leave only on the window thread the UI related code, so it can be accessed from several browser tabs at a time, and also have the option to easily use a WebSocket to a remote server running the logic of the application instead against the local WebWorker/SharedWorker (the API is almost the same, only one using send() method and the other usind postMessage() method. I truly don't know why that difference between both, but this a different story...). The problem is that trying to create the PeerConnection inside the WebWorker it tell me that both webkitRTCPeerConnection and RTCPeerConnection are not defined, so I suppose this use case was not considered by the specification. A temporal solution would be that the WebWorker send back the petitions to use the PeerConnection object to the window thread and process them there, but this would over complicate the application architecture and also decrease performance. Any clue about this topic? -- "Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton de sitios diferentes, simplemente escribe un sistema operativo Unix." – Linus Tordvals, creador del sistema operativo Linux
Received on Sunday, 24 February 2013 01:50:34 UTC