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

Re: XML Parsing using DOM parser

• To: "Niels Peter Strandberg" <nielspeter@n...>,<xml-dev@l...>
• Subject: Re: XML Parsing using DOM parser
• From: "Dare Obasanjo" <kpako@y...>
• Date: Thu, 3 Jan 2002 06:16:46 -0800
• References: <5537C5C4-FFD0-11D5-8DB9-000502CB905D@n...>

When last I looked, Xindice wasn't up to handling large files (> 5 megabytes).
I'd lookup one of the mailing list posts on this but I am unable to locate an
archive. However I did find that question #10 of the FAQ[0] answered this
question (although the FAQ might be outdated).


[0] http://www.dbxml.org/docs/FAQ

--
THINGS TO DO IF I BECOME AN EVIL OVERLORD #41
Once my power is secure, I will destroy all those pesky time-travel devices.

----- Original Message -----
From: "Niels Peter Strandberg" <nielspeter@n...>
To: <xml-dev@l...>
Sent: Wednesday, January 02, 2002 2:30 PM
Subject: Re:  XML Parsing using DOM parser


> The answer might be a simple, but it is hard to give any advice without
> knowing how you are using the document, how it is structured, and what
> kind of changes to the document you frequently do, etc.
>
> The answer might be a sax app or a xml db like dbXML (now Xindice)
> http://www.dbxml.org/
>
> Tell us some more!
>
> Niels Peter
>
> On onsdag, januari 2, 2002, at 07:29 , Deepa Venkatesan wrote:
>
> > Dear Gurus,
> >
> >            Kindly share your thoughts.. I recently
> > wrote a code to parse an XML file containing catalog
> > content (as big as 10MB) using DOM parser. The
> > performance has been miserable particularly when the
> > XML file size increased. The problem is that using a
> > SAX parser (the only other alternative that strikes
> > me) I would have to re write the complete XML and the
> > code for this would be really elaborate. My final
> > objective of parsing to change 2 lines for every
> > catalog item (the XML file has as many as 3000 catalog
> > items).
> >
> >     I am wondering if any of you have encountered such
> > problems and how you went about resolving it. Using
> > DOM parser is safe when it comes to maintaining the
> > identical XML structure particulary when I need to
> > make slight modifications on the original XML. But how
> > do I overcome the problem of the HUGE time taken to
> > convert the XML into a DOM tree. Any help is
> > appreciated.
> >
> > Thanks in advance,
> > Deepa
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Send your FREE holiday greetings online!
> > http://greetings.yahoo.com
> >
> > -----------------------------------------------------------------
> > The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> > initiative of OASIS <http://www.oasis-open.org>
> >
> > The list archives are at http://lists.xml.org/archives/xml-dev/
> >
> > To subscribe or unsubscribe from this list use the subscription
> > manager: <http://lists.xml.org/ob/adm.pl>
> >
>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

• Follow-Ups:
  • Re: XML Parsing using DOM parser
    • From: Niels Peter Strandberg <nielspeter@n...>

• References:
  • Re: XML Parsing using DOM parser
    • From: Niels Peter Strandberg <nielspeter@n...>

• Prev by Date: Re: XML Parsing using DOM parser
• Next by Date: RE: W3C's five new XQuery/Xpath2 working drafts - Still missing Updates
• Previous by thread: Re: XML Parsing using DOM parser
• Next by thread: Re: XML Parsing using DOM parser
• Index(es):
  • Date
  • Thread