Comments on: Asynchronous HTML and HTTP http://watchitlater.com/blog/2009/09/asynchronous-html-and-http/ A reluctant foray into the world of blogging. Tue, 13 Dec 2011 12:46:52 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Tom http://watchitlater.com/blog/2009/09/asynchronous-html-and-http/comment-page-1/#comment-4698 Tom Sun, 27 Sep 2009 00:33:26 +0000 http://watchitlater.com/blog/?p=49#comment-4698 That's what I found on a project where we used AHAH. We also did some cool extensions to SiteMesh allowing us to tell it to return the contents of a named div on the page rather than decorating the page. That way we did not have to have multiple versions of pages - just different decorations. That’s what I found on a project where we used AHAH. We also did some cool extensions to SiteMesh allowing us to tell it to return the contents of a named div on the page rather than decorating the page. That way we did not have to have multiple versions of pages – just different decorations.

]]> By: Adriano Almeida http://watchitlater.com/blog/2009/09/asynchronous-html-and-http/comment-page-1/#comment-4691 Adriano Almeida Sat, 26 Sep 2009 17:06:38 +0000 http://watchitlater.com/blog/?p=49#comment-4691 Hey Thomas, I've been trying this approach (AHAH) for some time now, and I can say that it's far easier to write your ajax code (JQuery's one line of code, for instance). Some might say that you'll have the drawbacks that you will be transferring a whole XML (html, in the case). Well, in majority of the situations this improvement is insignificant. Regarding the tests, if you do JavaScript unit tests (QUnit, or something like this), it'll also get easier to test, after all your code is simpler now (no "heavy" DOM manipulations). If you use a tool like Selenium to see if the ajax call is being correctly done instead, it won't change anything on your tests. Of course, there's still some cases that is more helpful to use AJAX, instead of AHAH. Hey Thomas, I’ve been trying this approach (AHAH) for some time now, and I can say that it’s far easier to write your ajax code (JQuery’s one line of code, for instance). Some might say that you’ll have the drawbacks that you will be transferring a whole XML (html, in the case). Well, in majority of the situations this improvement is insignificant.

Regarding the tests, if you do JavaScript unit tests (QUnit, or something like this), it’ll also get easier to test, after all your code is simpler now (no “heavy” DOM manipulations). If you use a tool like Selenium to see if the ajax call is being correctly done instead, it won’t change anything on your tests.

Of course, there’s still some cases that is more helpful to use AJAX, instead of AHAH.

]]>