we would share with you what some of the world's leading rich Internet application pioneers are thinking

There's a growing impedance mismatch between the large scale providers of content and the consumers of that content as we build multiple messaging architectures. How realistically do we resolve this mismatch in such a way that we are able to preserve both flexibility (SOAP), simplicity (Atom) and brevity (JSON), and can we do so without sparking a religious war?

Will the browsers development, unification and standardization give us more possibilities and freedom to sophisticate or simplify our interfaces & APIs?

Do you believe a shift back towards rich desktop apps, which are internet-enabled, will lead away from the need for AJAX-enabled web applications?

If you imagine the a URI is a handle to a given resource -- is the AJAX community pushing to retain the isomorphic relationship between the URI and a given state of a web application as it changes through AJAX interaction?

Are off-line applications for web the right direction? Is Google Gears relevant when more and more devices has 24/7 Internet access? Will web applications of the future be complex on client and lightweight on server side or rather the opposite? This is essential issue to me, as Tigermouse framework I develop favors the later approach.

Other questions like: [1] ambiguity in AJAX toolkits, can I match them? how an aspect in Toolkit A can influence toolkit B? The namespaced Web apps becomes now important. It's the same that happened in Browser space, they were different, then become a bit shared, the AJAX toolkits work also may reach a convergence state as we have offline/online caching infra-structure with namespaced events - sandboxed apps in the same page but running each in a given scope.

I think the next stage promises good things for us and the current stage is a mess with good value under it. The exploration of the mashup stack and mashup infra for interoperability is an area to massage.

If only AJAX could somehow bring us a spam-free internet, now THAT would be a rich future!

While Ajax represents the future, it looks like in Georgia they still have developers working in ColdFusion from Adobe - how come? Here's the link: [visit link]

Development managers need to ask themselves at least these two questions before adopting AJAX on a project. First, will you make up for the time invested in adopting a new technology through increased development speed? And second, will AJAX allow you to offer a more useful application to your users?

The answer is definitely: Java + XML + XSLT + a new ML, instead of: JavaScript + XML + HTML. But is there any project which take into account all these ideas? Are there any band of developers who are interested in re-inventing a better wheel?

The next stage of AJAX is Comet.

It was inevitable that someone would use web 2.0 social aspects together with an AJAX interaction layer to create a next generation weblog. As usual it took a seventeen year old to do it. Logahead is everything I've been looking for recently in blogging software. It's PHP, MySQL, AJAX, and has several social features.

DEMO LINK: [visit link]

The event-driven web is the most important step for a new Internet in recent years.