Friday, October 31st, 2008

Kaazing Gateway: HTML 5 WebSock Server Released

Category: Comet, HTML

<p>

Kaazing has released Kaazing Gateway, an open source HTML 5 WebSocket Server.

The HTML 5 WebSocket specification is a standard that attempts to simplify much of the complexity around achieving bi-directional communications between browsers and servers. The specification provides a simple JavaScript interface that enables developers to open a full-duplex socket connection and connect directly to any TCP-based back-end service (for example, JMS, JMX, IMAP, Jabber, and so on).

Kaazing Gateway makes it possible for developers to take advantage of WebSockets today by providing a JavaScript library that emulates the HTML 5 WebSocket, making it possible to build applications that leverage the WebSocket interface and that can be deployed to both modern and future browsers.

The ultra high-performance server behind Kaazing Gateway can support tens of thousands of concurrent connections on a single node. Multiple instances can be clustered with traditional HTTP load-balancers or DNS round robin, making it possible to support any number of persistent client connections. In addition to large numbers of connections, Kaazing Gateway can also handle high data throughput thanks to its high-performance, staged event driven architecture (SEDA).

The Atlantis release of Kaazing Gateway also comes prepackaged with JavaScript clients for popular message services such as Apache ActiveMQ and RabbittMQ as well as clients for XMPP services such as OpenFire, Jabberd, and other popular chat servers. This makes it easy for you to quickly build web-based chat applications or messaging applications such as stock matrixes, online trading platforms, or online games.

What is the WebSocket API?

javascript
< view plain text >
  1. interface WebSocket {
  2.   readonly attribute DOMString URL;
  3.  
  4.   // ready state
  5.   const unsigned short CONNECTING = 0;
  6.   const unsigned short OPEN = 1;
  7.   const unsigned short CLOSED = 2;
  8.   readonly attribute int readyState;
  9.  
  10.   // networking
  11.   attribute EventListener onopen;
  12.  
  13.   attribute EventListener onmessage;
  14.   attribute EventListener onclosed;
  15.   void postMessage(in DOMString data);
  16.   void disconnect();
  17. };

Related Content:

Posted by Dion Almaer at 6:06 am
5 Comments

++++-
4.6 rating from 83 votes

5 Comments »

Comments feed TrackBack URI

fantastic, websockets in older and newer browsers!

Comment by Ramon — October 31, 2008

Dion, that code sample is not javascript :)

Anyways, this sounds very interesting, but the documentation looks very poor.

Comment by LeoHorie — October 31, 2008

looks pretty amazing to me: http://www.kaazing.org/confluence/display/KAAZING/Home
“Web Socket protocol can be used to support a diverse set of clients: JavaScript, Adobe Flex, JavaFX, Microsoft Silverlight…”
with ActiveMQ demo.. too bad the link didn’t work dough…

Comment by Ramon — October 31, 2008

Hi Ramon,

Thank you for you comments. I apologize for the broken link. The link is actually meant to reference localhost on your local machine. There are a set of demos bundled with the download as well as the documentation you found online.

LeoHorie,

Thank for your interest. I greatly appreciate your critique. In response could you please provide some feedback to help us improve. I would greatly appreciate your help

Again, thank you both. Feel free to email at ric dot smith at kaazing dot com if you have any additional questions or comments.

Comment by RicSmith — October 31, 2008

@LeoHorie

This is the interface definition expressed in IDL from the HTML5 specification. This is meant to be language independent in case someone wants to implement the spec in some other language (e.g. .NET for silverlight).

Comment by fjakobs — November 1, 2008

Leave a comment

You must be logged in to post a comment.