> I am also looking into this and trying to remove the use of QName in
> ElemStack to improve performance .... No concrete code yet, but working
on
> it. Stay tuned.
>
Ok, I happened to notice this one and I'll come out retirement for one
message... The ElemStack should not have any effect in the scenario that he
put forward. He said he had 'lots of direct children of the root', but the
element stack is only used to check for nesting errors and such, so it never
gets more elements than the deepest nesting of elements in the document. So
it would never have more than a handful of elements in it in that case, even
if there a billion direct children of the root.
So if his document is really structured like he says, then he cannot
possibly be getting this result from the element stack, unless that code is
broken and not popping off as its supposed to. Now, where he could get such
a problem is if validation is on, because some content model is going to
have to track all of the element ids of the children of the root, in order
to validate it at the end.
But otherwise, something is not right here and some wires are crossed.
--------------------------
Dean Roddey
The Charmed Quark Controller
Charmed Quark Software
[EMAIL PROTECTED]
http://www.charmedquark.com
"If it don't have a control port, don't buy it!"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
