Rich Salz wrote:
> Yes, right now, it is probably not a performance issue that a streaming
> parser has to buffer everything until it sees the ">". That can only be
> addressed by anecdotal evidence. What is more important is that
> *architecturally* this is a bottleneck. As things get faster, all the
> other implementations (ew, a JVM? :) will fall away, and we'll still be
> left with this architectural problem. I betcha it's already an issue for
> some folks building XML parsers in hardware.
I don't believe that for a minute. As hardware gets faster, this will
too. As the VM and just in time compilers get better, this will too.
Other algorithms may get faster here and there, but they're not going to
zero. Unless someone has really good measurements to prove caching
attributes is a problem, I don't believe it.
You say, "I betcha it's already an issue for some folks building XML
parsers in hardware." Datapower builds XML parsers in hardware. Are you
saying this is an issue for you? If so, please elaborate. If not, why do
you think it would be an issue?
--
Elliotte Rusty Harold
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim
