Saturday, 4 December 2010

HTML 5 Web Sockets arrives in StreamHub 2.2.9

Some of you may have noticed HTML 5 Web Sockets sneaking into 2.2.x releases of StreamHub but now it's officially here. 2.2.9 brings full Web Sockets functionality for browsers that support it. Comet will still be supported for older browsers and those that don't yet support the latest HTML 5 standards. Detection of the most reliable connection-type is built-in, with transparent failover to Comet and Ajax Polling. This means you don't need to make any changes to your existing code to start using Web Sockets, StreamHub will automatically detect the best connection-type for you.

Current Web Sockets Support in Browsers

  • Google Chrome
  • Apple Safari 5+
  • Firefox 4 Beta
  • Apple iOS 4.2+ for iPad & iPhone

What else is new in 2.2.9?

2.2.9 has come a long way since the popular stable 2.0.x branch. So, here's a complete set of release notes for those looking to upgrade from 2.0.x.

  • Fixed (2.2.9): Web Socket handshake intermittent issues
  • Fixed (2.2.8): Expensive debug string operation being performed on all log levels
  • Fixed (2.2.7): Firefox 3.x Comet reconnection bug when hitting 300k limit
  • Fixed (2.2.7): MAX_CLIENT_LIMIT was disconnecting most recent WebSocket client
  • (2.2.7): HTTP file handling improvements
  • (2.2.7): Logging improvements
  • (2.2.7): Upgrade to support secure Web Socket handshakes
  • (2.2.4): Performance improvements
  • (2.2.4): HTML5 Web Sockets support
  • (2.2.4): Ability to monitor number of connected clients via JMX
  • Fixed (2.2.4): Possible NPE in Dispatcher
  • (2.1.x-beta): Numerous performance improvements to the HTTP handling.
  • (2.1.x-beta): Transparent failover to polling connections where firewalls/proxies prevent full duplex streaming.
  • Fixed (2.1.x-beta): Ajax adapter was not reconnecting if no serverList was specified.
  • Fixed (2.1.x-beta): 'Stopping polling' log message appeared even when not using a polling connection type.
  • (2.1.x-beta): More control over HTTP headers for pages and comet content.

Important note when upgrading from 2.0.x

If you migrate any existing Ajax SDK apps from 2.0.x to 2.1 or 2.2 you will need to change your connection URLs to incorporate the new streamhub context. For example, if previously you were using:


hub.connect("http://localhost:7979/");


You will now need to use:


hub.connect("http://localhost:7979/streamhub/");


Get the latest version

Find the latest 2.1.12-beta available to download below aswell as links to the most up-to-date documentation and tutorials:

No comments:

Post a Comment

Post a Comment