[Icer5k]

I'm curious what performance issues you were seeing in Firefox. I'm doing quite a bit of work with the same stack, and have been able to get sub-10ms decode times with Broadway.JS in all the major browsers. As long as you use transferable objects to pass data around, I haven't had any problems using web workers as decode threads either.

[EvanDotPro]

I'm sorry, I actually mixed up two different experiments regarding the performance issues (I've been playing with this stuff for a looongg time and have many different prototypes). Allow my to clarify. :)

The performance issues with using Broadway.js were more "general", in that the experience varied wildly, from amazing to unusable depending on the browser/device/etc)... Not necessarily related to Websockets + Webworkers.

The Websocket issue on the other hand, was for a more recent experiment where I was playing with the idea of bridging NoVNC over WebRTC data channels.

It's not so much a performance "issue" as much as a "possible area for optimization"... Though, every time I'm playing with noVNC or Broadway.js in a FF tab on my i7 laptop, it pretty much renders FF pretty laggy in all other tabs. I imagine offloading as much of the processing to workers as possible would be the best approach to lessen the effect — though, I'm not much of a frontend / JS dev.

Here's the noVNC issue: https://github.com/kanaka/noVNC/issues/114 And the bugzilla for FF: https://bugzilla.mozilla.org/show_bug.cgi?id=504553