Hi, I think I might use GWT for pretty much any AJAX website, if I can. There are so many reasons why even non-application-style sites can benefit from it, think
- Code splitting - ClientBundles - Improved internationalization - JS minification - Cross-browser-quirks mitigation - Refactoring, debugging, call hierarchy - ... And yes, Ajax Push (Comet + Asynchronous processing) is really nice for low-delay client side updates. The ape-project looks interesting (just discovered it thanks to your link). However, APE is definitely not the only solution to this. - For Comet, there's http://code.google.com/p/gwt-comet/ (also just discovered this), and - for asynchronous processing there's Continuations in Jetty, also the new Servlet 3.0 API supports it, and Tomcat provides a solution, too. Consider, that APE is GPL, so your project will probably have to be GPL compatible. Chris
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
