about Open Source Ajax Toolkits ?

hi authors,

this book have one chapter on "Open Source Ajax Toolkits" is this like introducing this toolkit to using for Ajax development?

and how this toolkit work can you give me any example (any link) and how this toolkit become more helpful in development of Ajax application?

Thanks,
[ April 10, 2007: Message edited by: Saif uddin ]

In that chapter, we survey how Prototype, jQuery and the Dojo Toolkit make Ajax requests easier to create and handle. The way that DWR uses Ajax to approximate an RPC protocol between Javascript and server-side Java is also examined.

Because these libraries handle the browser dependencies, as well as the details of the ready-state handling, I never write Ajax applications without using one of them. It just makes no sense to write all that low-level code when these libraries do it so well and so easily.

Originally posted by Saif uddin:
hi authors,

this book have one chapter on "Open Source Ajax Toolkits" is this like introducing this toolkit to using for Ajax development?

Note that ICEfaces (discussed in the Drag and Drop chapter) is now open source as well. ICEfaces allows you to transparently add Ajax to JavaServer Faces applications and provides support for Ajax Push.

Originally posted by Bear Bibeault:
In that chapter, we survey how Prototype, jQuery and the Dojo Toolkit make Ajax requests easier to create and handle.

jQuery! is this the new library? I have never heard this name before.
could you tell me the reason why you choose this library for Ajax development as you already use Prototype?

Thanks

jQuery is another very useful library that is rapidly gaining admirers and supporters. It only seemed fair to give readers a taste of more than one library so that they could choose which better suits their needs.

Thanks for answer Bear and Thanks for you Ted Goddard provide me little information on that Chapter..

Thanks again,

Authors, what's your take on the readiness of these libraries for picky corporate users? I did a brief Ajax survey a while ago and none of them had the kind of doc that my peers will expect and other reviewers haven't been too kind to the code quality. I didn't have the depth of JavaScript to judge code much myself, except that it was pretty darned hard to tell what they were up to at first glance. Should GWT give me better warm and fuzzy feelings, just because Google seems to be Very Smart People?

Originally posted by Stan James:
Authors, what's your take on the readiness of these libraries for picky corporate users?

Some of them are quite ready; in fact, some are even developed by picky corporate users! GWT is of course created by Google; if they're using it, they're probably getting some kind of benefit out of it. OpenRico is actually created by Sabre for their own purposes.

Should GWT give me better warm and fuzzy feelings, just because Google seems to be Very Smart People?

Seeing as how I work for Google, yes, you should get very warm and fuzzy feelings