[
Lists Home |
Date Index |
Thread Index
]
> The original question mentioned multiple catalog items in the same XML
> document and the wish to update each of these items. Both XML and the
> DOM are agnostic on whether this is a good, bad, or indifferent
> practice.
:)
Theoretically there is no reason for this to be a bad practice in the DOM,
especially if it's a DOM implementation that supports XPath (which in fact
then makes it a best practice) . However, we live in a world full of
limitationa and memory issues put an upper bound on the size of documents one
can manipulate in this manner and how quickly such manipulation can be done.
> (On the other hand, if the document is transient, such as when it is
> used to transport data from on database to another and your application
> is simply an intermediary performing a transform, then best practices
> are less clear.)
I've been thinking about this for a while and the only good practice I can
come up with for transiently constructed data is to use a DOM implementation
that supports XPath to perform such operations with minimal code and still
preserve document fidelity. Yet this practice would fail to handle large
documents well.
--
THINGS TO DO IF I BECOME AN EVIL OVERLORD #35
I will not grow a goatee. In the old days they made you look diabolic. Now
they just make you look like a disaffected member of Generation X.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
|
