Re: Optimizing and XMLC application

>>3) Pre-generate large chunks of the final DOM (a good majority of the
>> duplicated "rows" are from domain data, and fairly static).
>>4) Pre-generate the data has HTML at run-time, or even at compile time
>> (see #3 above)
>
> These could be a huge win.  Not only do you avoid DOM work, but the
> work of getting the data to populate the DOM.
>

Now the trick is, HOW.  Inserting a pre-generated DOM at run-time is not
too difficult, but I still pay the price of duplicating the DOM.  For this
to be a really big gain, I need to be able to spit out "raw HTML" in the
middle of an existing DOM.  The last time I asked about this (for entirely
different reasons), I got back a "it can't be done", I think.