Comments on: A Case Against Ajax Web Development Model http://beans.seartipy.com/2006/05/20/a-case-against-ajax-web-development-model/ "The time has come...to talk of many [technologies]." --Lewis Carroll('The Walrus and the Carpenter') Thu, 11 Mar 2010 08:25:51 +0000 http://wordpress.org/?v=2.9 hourly 1 By: Paul http://beans.seartipy.com/2006/05/20/a-case-against-ajax-web-development-model/comment-page-1/#comment-137073 Paul Tue, 29 Apr 2008 09:37:45 +0000 http://beans.seartipy.com/2006/05/20/a-case-against-ajax-web-development-model/#comment-137073 Great topic, very interesting read. Have added to mailing list. Many thanks Paul <a href="http://www.pagerankpro.info//free-pagerank-display.php" rel="nofollow"></a> Great topic, very interesting read. Have added to mailing list.

Many thanks
Paul

]]> By: Every Flavour Beans » Should I Be Developing Ajax Applications using Google Web Toolkit(GWT)? http://beans.seartipy.com/2006/05/20/a-case-against-ajax-web-development-model/comment-page-1/#comment-19 Every Flavour Beans » Should I Be Developing Ajax Applications using Google Web Toolkit(GWT)? Wed, 24 May 2006 11:33:34 +0000 http://beans.seartipy.com/2006/05/20/a-case-against-ajax-web-development-model/#comment-19 [...] So why should an Ajax developer be interested in the recently released Google Web Toolkit(GWT)? One possible reason could be to overcome the shortcomings of the typical Ajax web development model as noted in my earlier post. Firstly, a framework always provides a head start to a project, allowing the developers to worry only about writing the application logic; user interface elements, the plumbing work needed for the communication between the client and the server are provided by the framework itself. The more specific benefits of using the Google Web Toolkit are: [...] [...] So why should an Ajax developer be interested in the recently released Google Web Toolkit(GWT)? One possible reason could be to overcome the shortcomings of the typical Ajax web development model as noted in my earlier post. Firstly, a framework always provides a head start to a project, allowing the developers to worry only about writing the application logic; user interface elements, the plumbing work needed for the communication between the client and the server are provided by the framework itself. The more specific benefits of using the Google Web Toolkit are: [...]

]]>