http://pathfindersoftware.com/2007/09/parsing-html-wi/ The Fastest Way to Launch Successful Software Thu, 19 Jan 2012 16:36:03 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://pathfindersoftware.com/2007/09/parsing-html-wi/#comment-7055 Internetagentur Wed, 29 Apr 2009 15:00:12 +0000 http://www.pathf.com/blogs/?p=255#comment-7055 Thank you, this has me very helped. Thank you, this has me very helped.

]]> http://pathfindersoftware.com/2007/09/parsing-html-wi/#comment-7054 Jan Wed, 12 Sep 2007 10:08:36 +0000 http://www.pathf.com/blogs/?p=255#comment-7054 <p>A very good reason for using innerHTML is that it avoids duplicate code.<br /> You already know how to render data to a table on the server side.<br /> Implementing this a second time, in javascript, on the client side and keeping both implementations in sync blows up your codebase unnecessarily, is tedious and error-prone.</p> A very good reason for using innerHTML is that it avoids duplicate code.
You already know how to render data to a table on the server side.
Implementing this a second time, in javascript, on the client side and keeping both implementations in sync blows up your codebase unnecessarily, is tedious and error-prone.

]]> http://pathfindersoftware.com/2007/09/parsing-html-wi/#comment-7053 Anonymous Mon, 10 Sep 2007 23:35:28 +0000 http://www.pathf.com/blogs/?p=255#comment-7053 <p>Another reason to use innerHTML is because it's so much faster. I have a case where I use ajax to paginate a table's content (thousands of rows, so it calls back to the server); Building the table manually with the DOM is very unwieldy and slow, the easier and faster solution is just to return back an updated TABLE element and toss that in with innerHTML.<br /> A browser's parsing engine is generally going to be much much faster than its javascript engine.<br /> The end-user doesn't care about coding niceness, only about perceived speed of the site.<br /> Building a TABLE on the server side is also much easier than trying to build one in the DOM.</p> Another reason to use innerHTML is because it’s so much faster. I have a case where I use ajax to paginate a table’s content (thousands of rows, so it calls back to the server); Building the table manually with the DOM is very unwieldy and slow, the easier and faster solution is just to return back an updated TABLE element and toss that in with innerHTML.
A browser’s parsing engine is generally going to be much much faster than its javascript engine.
The end-user doesn’t care about coding niceness, only about perceived speed of the site.
Building a TABLE on the server side is also much easier than trying to build one in the DOM.

]]>