– some famous computer guy

You are absolutely right that accessing XML nodes through the DOM is damn slow – I try to never do that. However, I am playing with something that automatically wraps an XML structure as a JS object, which I am tentatively calling JSON for XML (J4X). I will post about that soon with some more benchmarking results and the benchmarking code.

Then just grab it by it’s name and set the parent window object equal to it. I’ve been dynamically rendering IFRAMES and posting them to the server to perform “AJAX transactions” rather than using XML at all. The resulting JSON object is already serialized into the browser on reply and ready for use.

In fact I’ve created a JavaScript DataBinding Object, then use JSON objects for data sent between the server & client. I’ll use a hidden div field to hold my html templates then i just map the control id’s etc for dynamic output. I guess the benefit in doing this is (I use .Net) I can continue to build my markup using server controls and then F-Wit-Em when I need to on the client side. This also allows my interface to serialize back into my server object if need be.

Further I’ve read in several places that any XML processing not done using XML/XSLT will be very slow in every browser. It’s the built in XSLT processor which results in the performance advantage. Thought that may interest you.

(Also C++ supplort “Object Notation” so it’s really handy to process quick on the server!).

Very Very Sweet Article!

Matt

what I am comparing is the time it takes to go from a string of XML or JSON retrieved using an XMLHTTPRequest object to an HTML snippit that is ready to be inserted into a web page using innerHTML.

I am pretty sure that XSLT is not “irrelevant” – if it is good enough for Google Maps then its good enough for me.

I will have the code up tomorrow.

Using XSLT to overcome this is frankly irrelevant, there simply aren’t enough xslt engines available to make it relevant.

I did like your blog postings and comments but i have soem problem if some1 could help me out.

Does anyone know how to pass html table data from parent to a child form html table ? Or may be you could let me know any URL related to this topic.

Any kind of help is highly appericiated.

Thanks

Imran Hashmi
http://www.visionstudio.co.uk

In my earlier posts I was specifically looking at the string concatenation time to build a table versus the XSL-T method. In those cases the concatenations are done using the string array push then join method – which was deemed the fastest method on Quirksmode: http://www.quirksmode.org/dom/innerhtml.html

In the experiments posted here I dynamically concatenate a large string of JSON depending on the number of records that I am using and then time only the code that says eval(JSONString) so I am careful to test as close to the source as possible.

By doing DOM calls instead of XSL-T you are thinking that the XML is HTML ready I suppose? This could certainly be faster in some situations.