Hello,
7000 lines? That might be a little bit more than XML for <SCRIPT> can handle, unless you're on a
very fast computer. XML for <SCRIPT> is dependant on the speed of JavaScript on each browser.
Sadly, JavaScript isn't the fastest thing around and as you get more and more nodes, XML for
<SCRIPT>'s performance starts to drag.
Sadly, there isn't a whole lot I've been able to figure out to do about this. The Classic DOM is
faster than the W3C DOM, but not a whole lot faster. My current idea is to try to somehow use the
C++ based parsers of the individual browsers, but that solution is still unproven.
I'm sorry if XML for <SCRIPT> won't work for you, but I'd rather tell you how it is than try to
lead you down a path I don't think will work for you...
Best regards,
David
--- nurti <nu...@em...> wrote:
> Thank's David,
> for your response.
> I have now another big problem!
>
> I have to parse an xml stream with 7000 line and w3cdom parser get much time for load this
> stream!
> Have yuo any suggest?
> You think that is better an applet that xml for script for this large stream?
>
> Thank's
>
>
> --
> Email.it, the professional e-mail, gratis per te: http://www.email.it/f
>
> Sponsor:
> Vieni a visitare il Garden Center Peraga. Seimila metri quadrati di esposizione per servire una
> clientela competente ed esigente.
> Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=1480&d=22-1
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/
|
