advantage of GWT over ordinary Ajax?

[NDP Prasad]

1.what is the advantage of using GWT when compared to ordinary Ajax implementation? (or) why GWT?


2.I felt there are some difference in implementing Ajax in PHP and JSP, Is both languages GWT implementations are covered in this book?

3.How is AJAX JSP Tag Library, Is GWT similar to that?
[ June 25, 2007: Message edited by: Bear Bibeault ]

[Bear Bibeault]

NDP Prasad, please take the time to compose meaningful subjects. Otherwise, this forum will be filled all week with posts all named "GWT in Action".

I have adjusted the title of this post for you.

[Robert Hanson]

Let me see if I can shed some light on this...

1. what is the advantage of using GWT when compared to ordinary Ajax implementation? (or) why GWT?

1. You write code in Java, not JavaScript.
2. Tons of Java tools available.
3. GWT compiler optimizes compiled code, smaller file size.
4. GWT compiler can optimize images, making page load faster.
5. Tools for i18n, RPC, XML, JSON, etc.

2.I felt there are some difference in implementing Ajax in PHP and JSP, Is both languages GWT implementations are covered in this book?

You are talking about the server-side here. GWT has its own proprietary RPC mechanism (GWT-RPC), where you would use servlets on the server.

Besides this you can use alternative methods, like REST, XML messages, and JSON. You can use whatever you want on the server. Some people use Struts, some Spring, some PHP, Perl, Ruby, etc, etc.

GWT is server agnostic.

3.How is AJAX JSP Tag Library, Is GWT similar to that?

No tags on the server. GWT is all about the code on the client-side. The only actual code it provides for the server is the GWT-RPC tool. There are a bunch of third-party projects out there though, like one for JSF integration, Spring integration, etc.