Lists Home |
Date Index |
I think some folks are missing the important implication of Dare's point.
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.
Rich Salz Chief Security Architect
DataPower Technology http://www.datapower.com
XS40 XML Security Gateway http://www.datapower.com/products/xs40.html
XML Security Overview http://www.datapower.com/xmldev/xmlsecurity.html