Guys,
I just published
0.9.14 to NPM which addresses a memory leak in Socket.IO WebSocket when running on SSL. Major thanks to
John Allen for his amazing research and patch contribution. Hopefully we'll see the underlying problem go away in Node.JS core soon with the upcoming
upgrade API.
For those who are curious about 1.0 (everyone), I'm happy to report that I'll be freezing all the work on the new underlying architecture with the upcoming
engine.io 0.6.0 release.
I have a very large body of updates to share with you about what's included in Socket.IO 1.0.
The project has been selected for a mentoring program run by Stanford and over the past few weeks I've been working with students on a lot of improvements and new features for the next major release.
We're unveiling the new blog and website over the next couple weeks through which the announcements will take place. Some of the major enhancements include:
- A new test suite that runs the new
socket.io client and server on dozens of mobile devices and desktop browsers every time we push.
- A very simple and robust approach to multi-node scalability
- Built-in streams support
- Fine tuning of all the transport APIs
- Official CDN support tied into NPM releases.
Thanks for your patience and stay tuned!
--
Guillermo Rauch