Socket.IO 0.8.6 released - big updates

[Guillermo Rauch]

Summary:

• Major speed optimizations (parser 50%-200% faster)
• Added benchmarks to build process
• HTML5 WebWorker support on the client
• More client caching options (/socket.io/socket.io.vx.x.x.js will send far-future Expires)
• Upcoming IE10 WebSocket support
• Server tests improvements
• Client acceptance tests improvements
• Lots of bug-fixes and minor enhancements.

Server

0.8.6 / 2011-10-27 

==================

  * Added JSON decoding on jsonp-polling transport.

  * Fixed README example.

  * Major speed optimizations [3rd-Eden] [einaros] [visionmedia]

  * Added decode/encode benchmarks [visionmedia]

  * Added support for black-listing client sent events.

  * Fixed logging options, closes #540 [3rd-Eden]

  * Added vary header for gzip [3rd-Eden]

  * Properly cleaned up async websocket / flashsocket tests, after patching node-websocket-client

  * Patched to properly shut down when a finishClose call is made during connection establishment

  * Added support for socket.io version on url and far-future Expires [3rd-Eden] [getify]

  * Began IE10 compatibility [einaros] [tbranyen]

  * Misc WebSocket fixes [einaros]

  * Added UTF8 to respone headers for htmlfile [3rd-Eden]

Client

0.8.6 / 2011-10-27 

==================

  * Added WebWorker support.

  * Fixed swfobject and web_socket.js to not assume window.

  * Fixed CORS detection for webworker.

  * Fix `defer` for webkit in a webworker.

  * Fixed io.util.request to not rely on window.

  * FIxed; use global instead of window and dont rely on document.

  * Fixed; JSON-P handshake if CORS is not available.

  * Made underlying Transport disconnection trigger immediate socket.io disconnect.

  * Fixed warning when compressing with Google Closure Compiler.

  * Fixed builder's uglify utf-8 support.

  * Added workaround for loading indicator in FF jsonp-polling. [3rd-Eden]

  * Fixed host discovery lookup. [holic]

  * Fixed close timeout when disconnected/reconnecting. [jscharlach]

  * Fixed jsonp-polling feature detection.

  * Fixed jsonp-polling client POSTing of \n.

  * Fixed test runner on IE6/7

Special thanks as always to the socket.io team, bug reporters & testers, and everyone who provided ideas!

--
Guillermo Rauch

LearnBoost CTO
http://devthought.com

[Mark Hahn]

I'm getting " Cannot find module 'socket.io-client'" when I do npm install socket.io. Anyone else having problems?

[Guillermo Rauch]

 ∞ tmp npm install socket.io

sock...@0.8.6 ./node_modules/socket.io 

├── polic...@0.0.4

├── re...@0.6.7

└── socket.i...@0.8.6

Try removing the npm cache (~/.npm) ?

On Fri, Oct 28, 2011 at 2:24 AM, Mark Hahn <ma...@hahnca.com> wrote:

I'm getting " Cannot find module 'socket.io-client'" when I do npm install socket.io. Anyone else having problems?

[Mark Hahn]

It was a problem on my end.  I had a supervisor set up to watch changes in the directory and it was somehow interfering.  Thanks for the help.

[Thomas Fritz]

Hi, great Release.

How does the worker support for the client work? What gets into this
worker, for what gets the workers used?

Some general words about information / documentation / etc.
I am relativly new to socket.io, and i have to say it is not as easy
as it could be to get the current documenation and/or manual for the
current release, with the current API Spec, examples, etc, etc.
Sometimes the socket.io website is a good start, most of the times
github has more information, but it is not clear if the README of
examples, etc are up-to-date.

I think this could really be improved to make an already gret library
even better. I actually really like the way node.js does it with its
documentation.

Kind regards

---
Thomas FRITZ
web http://fritzthomas.com
twitter http://twitter.com/thomasf

2011/10/28 Mark Hahn <ma...@hahnca.com>:

[Guillermo Rauch]

Thomas,

I'll be announcing the new docs very soon.

[Robert Steckroth]

Going to sleep with a big smile :)

--
Bringing game to younix
Bust0ut Entertainment  ---
PBDefence.com
"Finding the exit without looking"

[no1youknowz]

Great looking forward to that announcement! :)

[Gregory Hellings]

On Oct 27, 7:20 am, Guillermo Rauch <rau...@gmail.com> wrote:
> *Summary:*
>
>    - Major speed optimizations (parser 50%-200% faster)
>    - Added benchmarks to build process
>    - HTML5 WebWorker support on the client

I'm intrigued by this. Is there more information on it and how to
leverage it? Is it automatically utilized whenever support is detected
in the browser? Is there something special one must do to enable it?
How about for those of us who use socket.io in a non-node.js world?
How do we setup our systems to serve the files from the correct place,
etc?

--Greg

>    - More client caching options (*/socket.io/socket.io.vx.x.x.js* will send
>    far-future Expires)
>    - Upcoming IE10 WebSocket support
>    - Server tests improvements
>    - Client acceptance tests improvements
>    - Lots of bug-fixes and minor enhancements.
>
> *
> *
> *Server*

>
> 0.8.6 / 2011-10-27
> ==================
>
>   * Added JSON decoding on jsonp-polling transport.
>   * Fixed README example.
>   * Major speed optimizations [3rd-Eden] [einaros] [visionmedia]
>   * Added decode/encode benchmarks [visionmedia]
>   * Added support for black-listing client sent events.
>   * Fixed logging options, closes #540 [3rd-Eden]
>   * Added vary header for gzip [3rd-Eden]
>   * Properly cleaned up async websocket / flashsocket tests, after patching
> node-websocket-client
>   * Patched to properly shut down when a finishClose call is made during
> connection establishment
>   * Added support for socket.io version on url and far-future Expires
> [3rd-Eden] [getify]
>   * Began IE10 compatibility [einaros] [tbranyen]
>   * Misc WebSocket fixes [einaros]
>   * Added UTF8 to respone headers for htmlfile [3rd-Eden]
>

> *Client*

[Arnout Kazemier]

Socket.IO does not run it in web worker for you. It's just support so you can use Socket.IO from inside a web worker.

Example: https://github.com/LearnBoost/socket.io-client/blob/master/test/worker.js
https://github.com/LearnBoost/socket.io-client/blob/master/test/socket.test.js#L360-371