[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XML vs. object model resource usage for manipulation

• From: David Megginson <david@m...>
• To: xml-dev@i...
• Date: Tue, 10 Aug 1999 21:29:14 -0400 (EDT)

Rochelle Edens writes:

 > I'm actually more concerned about DOM manipulation and
 > parsing-activities in comparison to creating an object and method
 > invocations.  I understand there's a lot of overlap and
 > instantiating objects is inherent to both, and maybe I need to dig
 > through parser code and see how it's working and what's getting
 > created.  My thinking was that it could *potentially* be an issue.

Yes, it's certainly an issue.  The DOM is a generic object model for
XML documents, but when you already have a domain-specific object
model, it will usually be more efficient -- in those cases, people
tend to use an event-based API like SAX to build their object trees
directly, eliminating the middle DOM phase.


All the best,


David

-- 
David Megginson                 david@m...
           http://www.megginson.com/

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
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@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• References:
  • XML vs. object model resource usage for manipulation
    • From: "Rochelle Edens" <edensr@b...>
  • re: XML vs. object model resource usage for manipulation
    • From: David Megginson <david@m...>
  • Re: XML vs. object model resource usage for manipulation
    • From: "Rochelle Edens" <edensr@b...>

• Prev by Date: comparison between XML C/C++ parsers?
• Next by Date: re: comparison between XML C/C++ parsers?
• Previous by thread: Re: XML vs. object model resource usage for manipulation
• Next by thread: illegal namespace usage
• Index(es):
  • Date
  • Thread