Kaazing capitalizes on one of the most powerful aspects of WebSocket: that it can be used as a transport layer for other protocols. Thus the client itself can communicate using your own custom protocol -- or an existing public or third-party protocol -- over the Web through firewalls and proxies.

Unlike traditional solutions, the client does not need to go through an intermediary application server with HTTP to be translated to the real protocol on the back-end. The client is effectively communicating directly to your back-end server or application.

The Kaazing client libraries let you send binary messages in addition to text messages over a WebSocket connection. Kaazing WebSocket Gateway does not constrain you to only sending text messages.

Server-Sent Events (SSE) is defined as part of the HTML5 specification as an efficient non-polling mechanism to deliver downstream data.

Cross-Document Messaging is a feature of HTML5 which allows you to communicate between browser windows, tabs, or frames. The Kaazing client libraries have emulation for this feature when running in older browsers that don't support HTML5.

You can develop, test, and evaluate as much as you want for free. When you download Kaazing WebSocket Gateway it comes with a 50-connection free developer license. Other than that it is fully functional with no restrictions or time-limited features.

Go to the download page

Some of the HTML5 standards were designed to address the drawbacks of existing technology; HTML5 WebSocket is one such specification. Ajax and Comet are based on HTTP which was not designed for the requirements of modern-style browser applications.

HTML WebSocket is the next evolution in real-time communication over the Web, designed to be compatible with existing HTTP infrastructure, but without the limitations imposed by HTTP communication techniques.

The first thing most people notice about HTML5 WebSocket is that both the server and client can send data at any time, or even at the same time. This is in contrast to Ajax or Comet methods which rely on the client to regularly poll for data or perform other costly workarounds to simulate real-time communication.

Each message you send over a WebSocket has only two extra bytes to frame the beginning and end of the message. On the other hand, current HTTP communication such as Ajax or Comet include a large number of HTTP headers which are typically 1000 or more bytes. Therefore using HTML5 WebSocket can result in a drastic reduction in bandwidth, even on the order of 500x lower.

Any modern browser with native support for WebSocket can connect to the Gateway. But that's not all. Many environments can't or won't upgrade their browsers and Kaazing WebSocket Gateway makes sure they aren't left behind.

Kaazing's client emulation technology ensures older browsers can enjoy the benefits of Kaazing WebSocket Gateway with almost the same performance as native WebSocket. No plugins are required and browsers as old as Internet Explorer 6 are supported. Test it yourself by connecting to Kaazing.me with any browser.

Multiple levels of security for authentication, authorization, and encryption keep your data and your users safe — not just in the enterprise, but also over the Web. The HTML5 WebSocket specification has provisions for secure WebSocket connections. Kaazing WebSocket Gateway goes further offering a variety of authentication methods including the world's first implementation of Kerberos over WebSocket for secure authentication and authorization.

Modern browsers on mobile devices are also supported. For those without native WebSocket support, Kaazing's client emulation technology will let your applications run seamlessly.

You want to be able share the data from your back-end systems and applications over the Web without exposing them to everyone on the Internet. Kaazing WebSocket Gateway is ideal to place in the DMZ to act as a front-line access point for those back-end systems which can reside safely in the trusted network.

Allow cross-domain connections to your services and applications.

Fine-grained access control to specify which domains can access your services and applications. For example, you can have public services or a whitelist to only allow specific origin domains.

Manage and monitor Kaazing WebSocket Gateway connections and activity via JMX.

Get full end-to-end communication with your custom or third-party protocol, directly from the client to the back-end server or application. Developers use the standard WebSocket API in JavaScript. This allows you to connect standard Web applications to back-end servers transparently over WebSocket.

Get full end-to-end communication with your custom or third-party protocol, directly from the client to the back-end server or application. Developers use a WebSocket API in Adobe Flash, Flex, or Air. This allows you to connect standard Web applications to back-end servers transparently over WebSocket.

Get full end-to-end communication with your custom or third-party protocol, directly from the client to the back-end server or application. Developers use a WebSocket API in Silverlight. This allows you to connect standard Web applications to back-end servers transparently over WebSocket.

Get full end-to-end communication with your custom or third-party protocol, directly from the client to the back-end server or application. Developers use a WebSocket API from .Net. This allows you to connect standard Web applications to back-end servers transparently over WebSocket.

Get full end-to-end communication with your custom or third-party protocol, directly from the client to the back-end server or application. Developers use a WebSocket API in Java. This allows you to connect standard Web applications to back-end servers transparently over WebSocket.