XML vs. object model resource usage for manipulation

[David Megginson]

Rochelle Edens writes:

 > I'm investigating intra/intercomponent xml processing and am
 > wondering how this relates to traditional 'object model' processing
 > with respect to processor hits and memory usage.  Is one way going
 > to be less resource intensive than another?

They cannot really be compared -- XML is a mechanism for serializing
an object tree, while object trees are a mechanism for compiling XML
documents.  If you write everything out as XML and then read it in
again, of course you'll take a hit, but presumably you don't write it
out unless you have to do something with it (give the information to
someone else, save the state of your object tree between invocations,
or archive the information somewhere).

Think of your object tree as RAM, and XML as the hard drive -- RAM's
usually faster, but the information has to come from somewhere.


All the best,


David

-- 
David Megginson                 david at megginson.com
           http://www.megginson.com/

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)