Development of Ajax through OpenAjax Hub

OpenAjax has been in the forefront in the battle for Ajax interoperability since it was established in 2006. Leading the organization is IBM which has enticed most of the internet and technology giants. Even the usually reluctant Microsoft joined in the foray of OpenAjax believing that interoperability could be good after all instead of hogging all the limelight and alienating itself.

Frankly, the influence of OpenAjax Alliance is not felt yet but they are coming out with very powerful ideas that could actually change Ajax and make it an appealing for business setting.

The OpenAjax Hub

Among the innovations introduced by the OpenAjax Alliance is the OpenAjax Hub. The OpenAjax Hub is actually not only an idea but it has been implemented by various developers especially in a business setting.

The OpenAjax Hub is a truly remarkable set-up that could be applied to JavaScript and eventually in an Ajax based application. The size of OpenAjax Hub is less than 3Kb in size but it could be used to run different Ajax functions at the same time.

This is very applicable in streaming information from different sources or applying the results of the processes in the server in varying conditions (or another function) that could be implemented in the client side.

The OpenAjax Hub could be considered as a competition to Mash-ups. In a regular mash-up setting, developers use two or more frameworks and use the functions that are beneficial to them to build one Ajax based application. This is often time consuming since developers still have to wade through a couple of information and functions before they could select the right functions for the application.

On the other hand, the OpenAjax hub will enable the developers install different functions directly to an Ajax based application without even using frameworks. The OpenAjax Hub has different libraries which could be used by developers. Configuration is relatively easier in OpenAjax hub compared to mash-ups.

The OpenAjax Hub is already in its 1.1 Version. Unfortunately developers are not really aware of the development introduced by OpenAjax Hub in its version 1.0. When you compared the features and thrust offered by the 1.0 version to the 1.1 version, you can even say that the 1.0 version, although has laid the foundation, is more of an eye candy for the next thrust introduced by the OpenAjax Hub 1.1 version.

The OpenAjax Hub 1.1 version is aimed in increasing the security of the functions offered by the OpenAjax Hub. The Alliance aims to do this by implementing widget isolation. Widgets would still function as expected in an Ajax based application but they would be isolated so that developers could install heightened security practices in implementing widgets.

The heightened security practices could be introduced in every aspect of the Ajax based application but the outcome will not be as interactive. By using widgets, developers could also focus the important functions to improve the security measure.

By addressing the need for multiple functions and increasing security, the OpenAjax Hub should be able to implement highly interactive and secured Ajax based application.