- From: Trezy via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 Feb 2021 17:56:52 +0000
- To: public-webrtc-logs@w3.org
I'll provide my use case here in case this presentation hasn't been given yet. I'm working on a browser-based [MMORPG](https://en.wikipedia.org/wiki/Massively_multiplayer_online_role-playing_game). To make the game as efficient as possible, I'm working to move *everything* except for rendering off of the UI thread and into workers. My current work is centered around moving network communications into their own worker. My Worker has been processing messages from WebSockets, then using a `BroadcastChannel` to relay any updates to the UI thread. While WebSockets are great, TCP connections have plenty of well-documented issues in games networking. I'm trying to move to using a much better UDP connection via the [Geckos.io](https://geckosio.github.io/) library. The problem I'm encountering is that @yandeu's library requires `RTCPeerConnection` to be available. If we added the ability for an `RTCPeerConnection` to be transferred to a Worker, then I could initialize the Geckos.io library in the UI thread, then pass it off to my network communications Worker to replace what is currently a WebSocket connection. -- GitHub Notification of comment by trezy Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/64#issuecomment-781527929 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 18 February 2021 17:56:54 UTC