Hi. First, let me congrats you for this new book. I always liked the books which build a complete set of applications, not a snippet here and there. Do you think that GWT deliver to us what is trying to promote? Have you find any cons? Thanks.
Thanks! I wanted show how to handle some of the more complex issues that only arise out of full application development. Learning the tools is one thing but the techniques that evolve out of practical use are just as, if not more important.
I do believe GWT is great at what it promotes. Its easy to build big and fast applications. The GWT team is constantly improving things even when I've thought things were nearly perfect.
I find that Ajax is a great way to deploy applications. They're cross platform, nearly every computer has a browser, they're more responsive than web pages, and they're easy to write with GWT. I would say the cons would be with Ajax, not necessarily GWT. Ajax is limited by browser limitations. In your client you cannot access the file system, (a pro for security), or OS based API's. You're also limited to two simultaneous HTTP connections per domain and the Same Origin policy enforced by browsers, (more about these restrictions in the book).
Ajax isn't suitable for things that would be suitable in flash. For example, movies or graphical animations.