Wednesday, February 6th, 2008

OpenAjax Alliance Launches Its Second Wave

Category: OpenAjax

<>p>The 100+ members of OpenAjax Alliance recently approved the release of OpenAjax Hub 1.0, including the OpenAjax Hub 1.0 Specification, an open source reference implementation at SourceForge, and a complete test suite. OpenAjax Hub 1.0 is a small JavaScript library (<3K) that allows multiple Ajax toolkits to work together on the same browser frame. The central feature is a publish/subscribe event manager, which enables loose assembly and integration of Ajax components. OpenAjax Hub 1.0 allows multiple conformance options for Ajax libraries, some of which require only a couple of lines of new code. Some existing Ajax libraries, such as Dojo 1.0, bundle OpenAjax Hub 1.0 within their distribution.

The alliance’s second-generation initiatives will focus on secure mashups. OpenAjax Hub 1.1 will add support secure mashups, publish/subscribe across browser frames, and publish/subscribe between clients and servers (including Comet-based communications). A complementary second initiative, OpenAjax Metadata, will define industry standard Ajax library metadata that will be used by Ajax developer tools (i.e., IDEs) and mashup editors to create improved user experiences. OpenAjax Metadata will define:

  • Standard XML metadata for “widgets”, where widgets can be either the various UI controls found in Ajax toolkits or can be mini-applications such as Google Gadgets that can be used as components within a mashup. This metadata will allow Ajax IDEs to auto-populate widget palettes and property editors.
  • Standard XML metadata for JavaScript APIs, which will allow Ajax IDEs to deliver intelligent code-assist features to JavaScript developers.

The alliance also will provide open source transcoders that allow existing proprietary widget/gadget technologies, such as Google Gadgets, to work with Hub 1.1 and OpenAjax Metadata, plus an open source mini mashup framework that leverages OpenAjax Hub 1.1 and OpenAjax Metadata. Early versions of these open source initiatives can be found at the OpenAjax Alliance project at Sourceforge.

Related Content:

Posted by Dion Almaer at 8:13 am
5 Comments

+++--
3.4 rating from 33 votes

5 Comments »

Comments feed TrackBack URI

Your link is wrong. Here is the correct url: http://sourceforge.net/projects/openajaxallianc/

Comment by tj111 — February 6, 2008

I posted an article on OpenAjax.Com
OpenAjax Alliance needs to change!

The biggest problems:
1) Most developers do not even know what ‘OpenAjax’ is
2) There are NO jobs for “openAjax’ – Go over to favorite job search and see for yourself (I would suggest Indeed.Com)
3) The alliance still seems to cater to corporations instead of developers as a whole
4) Jon Ferraiolo STILL has NOT followed through with a simple promise when I donated the domain – he does not seem to appreciate the contribution or understand Open Source attribution .

Comment by OpenAjax — February 6, 2008

I agree that they’re a silent (and maybe aloof) bunch.

But about the tech; OpenAjax (or something like it) is really important. I especially like the ambition to create a standard Widget format, and for the focus on modularization. All the things done to ensure simplification for IDE’s will also make it easier for anyone to consume and manage services in general.

Cheers,
PS

Comment by peter svensson — February 6, 2008

We do need ‘OpenAjax’ – the Alliance has done some great stuff. The problem is it is to SLOOOOW

Comment by OpenAjax — February 6, 2008

We have implemented something similar at Appcelerator. We have a simple JS-based widget API that makes it easy to not only create new widgets, but to also wrap existing third-party widgets like those from YUI or ExtJS. Our widget API allows you to specify metadata (e.g., optional/required widget parameters, name, description, etc.), and this information is used by our Eclipse-based IDE.

We also have a simple publish/subscribe messaging model that handles both local (within the client application) and remote (Ajax) messages (also integrated with our IDE).

Of course, our implementation is not a standard, but it does attempt to address the some of the problems mentioned above.

Comment by nolan — February 7, 2008

Leave a comment

You must be logged in to post a comment.