Jonas Jacobi, Kaazing

Ajax killed the click-and-wait experience we once associated with the Web and today, Comet is eliminating the stale data-delivery associated with traditional Ajax techniques such as polling. However, based on recent progress within WebSockets in the HTML5 specification, Web developers can finally make streaming data to browsers in real-time a reality.

Kaazing Gateway is an Open Source, enterprise Comet solution that enables full-duplex communication from the browser to any TCP-based back-end service. Kaazing Gateway is the first Java solution that understands the WebSocket protocol and provides support for all major enterprise protocols (for example, JMS, IMAP, JDBC, Jabber, and so on).

Kaazing Gateway eliminates the need for using convoluted server- and client-side architectures to map server-side protocols to the browser over HTTP. The resulting, simplified architecture allows Web developers to use the browser's native JavaScript support to code directly against the back-end services without the need for custom Servlets or server-side programming.

That's right! Kaazing Gateway allows developers to take full advantage of the HTML 5 WebSocket interface today. Once browsers support full-duplex connectivity, per the HTML 5 specification, there is no need to change any server or client code; applications will automatically take advantage of the native browser implementations of HTML 5´s WebSocket interface with improved performance. This makes browsers first-class participants in the server-side message bus, allowing browsers to send and receive messages in text and binary form using standard server-side protocols, and to communicate directly with any back-end services over the Internet.

Kaazing Gateway also brings the elastic scalability required to support hundreds of thousands of concurrent users to Comet, as well as the performance necessary to guarantee service-level agreements within milliseconds. Come see how you can start changing the way the Web works!

There are several innovations within the HTML 5 specification that will forever change the direction of the Web, and one in particular - WebSocket - that will revolutionize the way we develop and deploy Web applications. Until now, bi directional browser communication has been an elusive goal of the Comet community, usually achieved with an assortment of hacks. However, with recent updates to the HTML 5 specification, developers can now use a full-duplex communications channel that operates over a single socket.

The HTML 5 WebSocket enables communication from the browser to any TCP-based back-end service (for example, JMS, JMX, IMAP, Jabber, and so on). For example, it is now possible to avoid convoluted architectures by simply channeling certain protocols to the browser over HTTP and Web applications can now be deployed without the need for a traditional Web server.

The speaker will provide an in-depth look into the use of HTML 5 WebSocket and the techniques and technologies required to build Comet applications with it. Additionally, the speaker will discuss the trade-offs between emerging de jure standards (such as HTML 5's WebSocket) and de facto standards such as the Bayeux protocol. Furthermore, the session will cover the server and network architecture that powers an event-driven Web application. Attendees will be introduced to the technologies and requirements for delivering scalable, real-time Comet Web applications, and, most importantly, to the pitfalls they may face in the process.

Bring your laptop to this tutorial!