Build Your Own AMQP Client
This a great article by Ben Hood on how-to
“Build your own AMQP client”.
This a great article by Ben Hood on how-to
“Build your own AMQP client”.
A native implementation of HTML5 Web socket is now available in the truck of the Firefox code base. That means that a native interface for Web socket should be generally available in Firefox in a few short months. You can track the feature here. So, WebKit when you do expect to catchup?
I just sat in on a talk by David Pallock on the Lift framework here at QCon London. What struck me most about the talk is how well Scala lends itself to the concept of the real-time Web–a concept that we try hard to evangelize at Kaazing. With Lift, many of the view components are Comet enabled which allows for real-time Web platform. Very cool, I must say. Even cooler, if we can sprinkle a little bit HTML 5 on there.
Also, David has a very nice, relaxed, conversational style of presenting that is very conducive for questions. Its obvious he is driving for understanding rather than pushing a pre-canned set of ideas, and I think he does a good job of educating rather than marketing. Well done David!
If you are in the area, I will be representing Kaazing at QCon London March 9-13. You can either drop by our booth to hear the latest about HTML5 and Kaazing Gateway or sit in on one of two talks. The first is a 3 hour tutorial that will give you some hands-on exposure to development with HTML5 WebSockets. The second is a talk where we will dive into the details about how Kaazing makes HTML5 available today.
I recently read “DWR Java AJAX Applications” by Sami Salkous–a PACKT Publication. At first, I was put off by the books short length and cover price of $39.99 US. However, after reading the book-to-cover twice I was pleasantly surprised to find that book not only adequately covers the subject of DWR, but covers it well. This is an excellent book if you are just starting to dabble with DWR. The book is jam packed with excellent code samples. It also provides solid coverage of deployment. I will recommend this book to any novice. Where I find the book falls short, but am not certain that it was ever meant to cover, is on the topics of performance and scalability. The book also only provides deployment examples for Apache Geronimo. It would be nice to add a few more examples for Jetty and JBoss. The development setup in the book is also specific to Eclipse. One additional nice to have would be an example of how-to structure a DWR project with Maven. Despite these minor shortcomings the book is a good read and the author should be proud of this publication. Nice work Sami! Now, if I can just get PACKT to lower their price a tad.
Sidda recently wrote a good piece on WebSockets for IndicThreads that provides a nice overview of the technology as well as a contrast to existing Comet transports. Sidda will also be speaking at IndicThreads in Pune, India next week.
The Kaazing team is dedicated to delivering the absolute best product possible and we feel the only way to accomplish that is to build the product you want. As such, we are working to improve our current documentation offering and would like to hear your feedback on how we can make our current and future documentation better. As a reward, we are offering an iPod Nano as well as a Kaazing T-Shirt for the first 5 respondents. Please visit kaazing.org for more information.
This question gets asked a lot and the answer really could not be much simpler. To download the source from kaazing.org simply issue the following subversion command:
svn co https://www.kaazing.org/svn
Thats it! To build the source download and install maven, then issue the following command in the top-level directory, which contains a pom.xml file:
mvn clean install
Done!
Kaazing, Kaazing Enterprise Gateway, Kaazing Gateway, WebSocket, WebSockets
Kaazing Gateway 8.09_2 was released last night and is now available at kaazing.org. This release includes a handful of bugfixes and two major features. The first is group chat. The XMPP client bundle with Kaazing Gateway now facilitates group discussions. This features is current being used by the guys behind Silicon Valley Code Camp to build a chat application that allows conference attendees to converse about a particular talk in virtual rooms, and review discussion about previous presentations.
The second, and most important feature, is a new license. Kaazing Gateway was initially made available via a modified Mozilla Public License, which contained an attribution clause. Today, Kaazing Gateway is made available via the OSI approved Common Public Attribution License (CPAL). CPAL is a weak copyleft license and a derivative of the Mozilla Public License. The primary differences between MPL and CPAL is the addition of sections 14 and 15. Section 14 permits an attribution notice with the following information: copyright notice, short phrase (10 words), graphic image and URL. Note, that Kaazing has chosen to leave this form of attribution at the desecration of the end-user. We do not require or mandate attribution, which is a bit of a departure from our old license.
Section 15 provides a networking provision, which is based on the “external deployment” approach from the Open Source License (rather than the Affero/AGPL approach). The provision requires that a company that makes the software available over a network provide the source code to persons who use such application over the network. In short, you can summarize CPAL as a friendly version of AGPL.
Outside side of the addition of sections 14 and 15 the CPAL is identical to the MPL. CPAL and MPL are also compatible so it is easy to combine works under either license. It should be noted that CPAL takes precedence when a work distributed under CPAL license is combined with any other work made available under MPL.
Kaazing, Kaazing Enterprise Gateway, Kaazing Gateway, WebSocket, WebSockets