默认情况下，将WebSocket服务添加到应用程序常常被误认为是高性能，但是，要想获得最佳性能，就必须在客户端和服务器上进行更多考虑。诸如SPDY，WebSocket和即将推出的HTTP 2.0之类的实时技术都有其自己的一整套障碍和反模式需要克服，本讲座将提供您所需的清单，以微调应用程序的实时性能。
在本次演讲中，我们将回顾WebSockets在实时技术领域中的适用位置，然后介绍创建安全，高性能，实时应用程序的最佳实践。
我们将详细审查以下内容：
使用安全WebSocket（WSS）相对于不安全（WS）
Polyfill性能
WS子协议以及与WebSocket服务交互的不同样式。
二进制传输和优化
压缩
电池寿命并优化长寿命会议。
Could not find any points on High performance and scaling.
I was expecting a talk about high performance, but it was a general overview of the technology and almost nothing about how to achieve high performance.
json is not ideal for sockets… Especially if you are sending/receiving messages 30-60 times a second (aka a game)
it seen waste time. not working bro. i write what u tell and test. noting happen. also u r not teling where u include server, server_websocket.js , u r caling they from where? i will feel happy in someone share a simple file which working well. thank you
Thanks for a nice overview, in your description however you mention Battery life and optimizing long lived sessions. I did not see that addressed in your video and that's how I found your video. I need to setup a real-time data push to a few dozen mobile devices running android and chrome and push data to them as soon as there are data changes. But I also need them to last as long as possible before they require battery swaps. Can you please go over best practices for doing real-time (or close to real time) data push to multiple connected mobile clients while conserving their battery power as much as possible.
Great talk! Thanks for sharing.
This is a very useful overview of a technology which is has not been described very well from a broader implementation perspective online. We see plenty of dense, technical documentation about WebSockets and lots of tiny code examples which do not give any real context whatsoever. In fact, what I really liked about this talk was that it showed me that I don't actually need WebSockets for my project, even though I have hacked something together and it's working, my approach to using them was skin-deep (because of the poor examples online) and shakey, and it would actually be more appropriate for me to use server-sent events instead. This video really helped me to see the broader requirements and I am very grateful for this talk, Wesley. Thank you!