note
Masem
I didn't realize this existed as well; however, I would suspect that in the DBI->XML->XSLT path, the choice of which parser or XSLT library that you use is going to have some, but not a significant impact on the overall speed, assuming that, as with LibXSLT and XML::Parser, there's a non-perl component. As demonstrated by the two pure-perl routes, any significant processing of XML is going to need a boost by having pre-compiled code available for at least parsing the system.
<P>
However, I think I'll add the XML::XSLT case as well as skipping the DOM->string->DOM conversion that I do as [gellyfish] mentioned in reply to [Matts] response above, as additional tests, just for completeness. (I could also probably improve the xslt sheet itself, for the row coloring code doesn't seem to be overly efficient).
<P>
I also understand that GNOME's LibXML (which XML::LibXML uses) is not fully complient with recent W3C specs, so that may be a notch against it, as I'd expect a fully complient library to be a bit more rigorous and thus more CPU demanding.
<P>
-----------------------------------------------------
<BR>
<I>
<A HREF="http://mneylon.masemware.com/">Dr. Michael K. Neylon</A> - <a href="mailto:mneylon-pm@masemware.com">mneylon-pm@masemware.com</a>
||
"You've left the lens cap of your mind on again, Pinky" - The Brain
<BR>
<FONT COLOR="#800000"><I>"I can see my house from here!"</I></FONT>
<BR>
<FONT COLOR="#808080"><I>It's not what you know, but knowing how to find it if you don't know that's important</I></FONT>
</I>
143791
143886