What do they mean with WebSockets hole punch on port 443 and Let's Encrypt? The first thing that comes to mind is running a TLS web/WS server on the endpoints, but I didn't think you can do TCP+TLS servers with WebRTC. Or can you?
A new open source server side WebRTC implementation would be very welcome, though this does seem to use some of the old C++ libraries too. I wonder how much exposure of C++ to hostile bits they managed to reduce?
That entire section reads like nonsense to me (and I understand NAT hole punching), seems like some kind of confusion. Why do you need special TLS certs for WebSockets, but not WebRTC? WebRTC is end-to-end encrypted like TLS, using a Diffie-Hellman exchange so that the signaling server doesn't see private keys.
My first guess is 2012 lacked easily accessible hardware accelerated h.264 encoding on the host and the cheaper clients lacked easily accessible hardware accelerated h.264 decoding. Now you can find hardware accelerated decode in your $20 IoT device.
Maybe pricing arbitrage? Every gamer I know has like 20-30 titles in their queue they want to try out. To purchase all of them only for a few moments play would be prohibitive. Pay per use makes more sense if it falls below current gpu cloud cost (~$1/hr).
What's amazing is that if you can deliver video games at 4K 60fps. You can deliver all but the most intensive any application this way.
The author here, I apologize for any confusion from my writing. We do use WebRTC in a server-like fashion. The browser attempts to establish a P2P connection with the host computer, and the peer negotiation is similar to if you wanted Chrome to talk to Firefox for a video call. The network of either end could both cause connectivity to fail which is when we fall back to direct WebSockets rather than a costly TURN server.
I will avoid getting into how our streaming performs vs. theirs because we have a lot of resources on why our tech is so fast[0]
That being said, as far as I know, Parsec's new browser-based client suffers from all the issues I mentioned in this blog and at the end of the day, our user experiences are completely different. Rainway being self-hostable you can put it on everything from Azure[1] to your home computer. We have a very unique "Games First"[3] approach and view ourselves more as a gaming service than a piece of game streaming software. As we continue to fledge out our voice, I think you'll be pleased with the results.
[+] [-] fulafel|7 years ago|reply
A new open source server side WebRTC implementation would be very welcome, though this does seem to use some of the old C++ libraries too. I wonder how much exposure of C++ to hostile bits they managed to reduce?
[+] [-] cjbprime|7 years ago|reply
[+] [-] fabricexpert|7 years ago|reply
but they couldn't make it work commercially and shut down in 2015.
Bandwidth hasn't really gone up, so what will be different this time round?
Edit: they actually laid off all employees in 2012, then relaunched and still failed in 2015
[+] [-] zamadatix|7 years ago|reply
Also I don't think your statement that bandwidth hasn't really gone up is true. https://www.statista.com/statistics/616210/average-internet-...
[+] [-] ArtWomb|7 years ago|reply
What's amazing is that if you can deliver video games at 4K 60fps. You can deliver all but the most intensive any application this way.
[+] [-] Malp|7 years ago|reply
[+] [-] monetus|7 years ago|reply
This is really interesting. I am very eager for browsers to improve their real-time audio/video potential.
[+] [-] kupiakos|7 years ago|reply
[+] [-] benbristow|7 years ago|reply
[+] [-] jeremycarter|7 years ago|reply
[+] [-] k__|7 years ago|reply
Wouldn't this get rid of the NAT problem all together?
I even read that people had scaling problems with P2P WebRTC.
(I know that WebRTC is intended to be used as P2P technology, but noone stops you from treating the server as a client)
[+] [-] andrewmd5|7 years ago|reply
[+] [-] wpdev_63|7 years ago|reply
[0]:parsecgaming.com
[+] [-] andrewmd5|7 years ago|reply
That being said, as far as I know, Parsec's new browser-based client suffers from all the issues I mentioned in this blog and at the end of the day, our user experiences are completely different. Rainway being self-hostable you can put it on everything from Azure[1] to your home computer. We have a very unique "Games First"[3] approach and view ourselves more as a gaming service than a piece of game streaming software. As we continue to fledge out our voice, I think you'll be pleased with the results.
[0]:https://blog.rainway.io/here-whats-new-in-rainway-0-5-0-3a66... [1]:https://www.youtube.com/watch?v=OlMq-3hmm5Y&list=PLaVZpLEYEQ... [2]:https://blog.rainway.io/our-core-mission-games-first-78671e4...
[+] [-] unknown|7 years ago|reply
[deleted]
[+] [-] ganaz|7 years ago|reply
[+] [-] mahgnous|7 years ago|reply
[deleted]