<<< Previous speaker next speaker >>>

Director of Product Strategy Ric Smith, Kaazing

Director of Product Strategy Ric  Smith

Ric is responsible for Kaazing's product strategy. Prior to joining Kaazing, Ric was Principal Product Manager for Oracle Application Development Tools. In his role as Principal Product Manager he was responsible for the evangelism and product direction of Oracle ADF Faces Rich Client as well as Oracle's AJAX and Java EE Web Tier offerings.

Prior to joining the application server team, Ric worked for Oracle's consulting business as a Principal Consultant, specializing in Java EE and AJAX development. In addition, Ric is a frequent speaker at International events and has written articles featured in industry publications such as Java Developer's Journal and AJAX World Magazine. Ric is a representative to the OpenAjax Alliance and a graduate of the University of Arizona.

Presentation: "Architecting for Performance and Scalability: Panel Discussion moderated by Floyd Marinescu"

Time: Wednesday 10:45 - 11:45

Location: Rutherford Room

Abstract: What does it take to scale? This panel will bring together leading architects and solution providers in the area of performance, scalability, fault tolerance, and clustering; the panel will explore current and emerging architectures, practices, and solutions for achieving predictable performance & scalability.

Presentation: "Kaazing Gateway: An Open Source HTML 5 Websocket Server"

Time: Wednesday 14:15 - 15:15

Location: Rutherford Room


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.

Presentation: "HTML 5, Web Sockets and Comet"

Time: Wednesday 15:45 - 16:45

Location: Fleet Room

Abstract: Dionysios Synodinos interviewing Jonas Jacobi and Ric Smith

Training: "The Future of the Web: HTML 5, WebSocket, and Comet"

Track: Tutorial

Time: Monday 13:00 - 16:00

Location: Henry Moore Room


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

The HTML 5 WebSocket enables communication from the browser to anyTCP-based back-end service (for example, JMS, JMX, IMAP, Jabber, and soon). For example, it is now possible to avoid convoluted architecturesby simply channeling certain protocols to the browser over HTTP and Webapplications can now be deployed without the need for a traditional Webserver.

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

Bring your laptop to this tutorial!