>This is a major design flaw in DOM. XOM does not not have this problem.
:-)
This is a major performance tradeoff deliberately accepted in the DOM.
Checking every string every time would impose serious overhead on
applications, completely unnecessarily in many cases since the structure of
the application itself guarantees that the failure will never arise. The
tradeoff is that the application is responsibile for doing this check, or
for using a support library which does it. The DOM spec lets the
implementation decide which point in that trade-off to accept.
So this isn't a DOM versus XOM comparison. It's a matter of picking the DOM
implementation that matches your needs. If you need to have it check your
code, use a DOM that does. If you're willing to take responsibiltiy for
ensuring the data's correct, you can use one that doesn't, and run faster.
The standard Xerces DOM doesn't run that kind of check-every-argument
safety net. It might be interesting to ship with an alternative version
that does, just as a debugging tool...
______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredictably the day Tim Berners Lee
got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
