Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 59651 invoked by uid 500); 31 Oct 2001 13:02:39 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 59639 invoked from network); 31 Oct 2001 13:02:38 -0000 Message-ID: <3BDFF6A5.8B1D6A9B@anyware-tech.com> Date: Wed, 31 Oct 2001 14:03:33 +0100 From: Sylvain Wallez Organization: Anyware Technologies X-Mailer: Mozilla 4.7 [fr] (WinNT; I) X-Accept-Language: fr,en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: ThreadSafe Parser References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Sam Ruby a �crit : > > Sylvain Wallez wrote: > > > > According to the JAXP spec, small synchronized blocks around calls to > > SAXParserFactory.newSAXParser() and > > DocumentBuilderFactory.newDocumentBuilder() should to the trick. This is > > faster than pooling that involves much more code, including some > > synchronized blocks. > > My experience has been that pooling is considerably faster, at least with > Xerces1. > > - Sam Ruby > I guess you're talking about pooling Parser instances, while I was talking about Factories. You're right : the way to go is certainly pooling Parser instances rather than pooling factories as we do it today. I'll change that, thanks for the hint. Sylvain. -- Sylvain Wallez Anyware Technologies - http://www.anyware-tech.com --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org