Return-Path: Delivered-To: apmail-xml-xerces-c-dev-archive@www.apache.org Received: (qmail 70207 invoked from network); 4 Sep 2003 10:02:57 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 4 Sep 2003 10:02:57 -0000 Received: (qmail 92712 invoked by uid 500); 4 Sep 2003 10:02:21 -0000 Delivered-To: apmail-xml-xerces-c-dev-archive@xml.apache.org Received: (qmail 92679 invoked by uid 500); 4 Sep 2003 10:02:20 -0000 Mailing-List: contact xerces-c-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: xerces-c-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list xerces-c-dev@xml.apache.org Received: (qmail 92644 invoked from network); 4 Sep 2003 10:02:19 -0000 Received: from unknown (HELO knox.decisionsoft.com) (212.18.248.26) by daedalus.apache.org with SMTP; 4 Sep 2003 10:02:19 -0000 Received: from somme.dsl.local ([10.0.0.44]) by knox.decisionsoft.com with esmtp (Exim 3.35 #1) id 19uqSJ-00048W-00 for xerces-c-dev@xml.apache.org; Thu, 04 Sep 2003 10:31:07 +0100 Date: Thu, 4 Sep 2003 10:31:07 +0100 (BST) From: Gareth Reakes X-X-Sender: gareth@somme.dsl.local To: "xerces-c-dev@xml.apache.org" Subject: Re: which parser shall I use? In-Reply-To: <2EA918FE7CC6FB4BA0510D671ADB2AB40474A343@elsoxfvexch01.elsevier.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Loop: systemfilter.decisionsoft.com X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi, > 1) DOMBuilder The DOM Level 3 parser. This may, amongst other things, change name before it gets to Candidate Recomendation. On the other hand, it will be the standards complient way to go. Its what I use internally. > 2) XercesDOMParser This is the way we parsed before DOM specified how we should. This is stable and widly used. > 3) SAX2XMLReader This is for SAX2. > 4) SAXParser This is for SAX1. > 5) deprecated DOMParser Don't use this. > > Which parser should I use? Which parser is fastest? If you don't need to build a full DOM Tree then SAX will be much faster (but you will have to specify what happens in each of the handlers - see the samples). If you do then either XercesDOMParser or DOMBuilder depending on the level of stability you require. Gareth -- Gareth Reakes, Head of Product Development +44-1865-203192 DecisionSoft Limited http://www.decisionsoft.com XML Development and Services --------------------------------------------------------------------- To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org For additional commands, e-mail: xerces-c-dev-help@xml.apache.org