Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 212 invoked by uid 500); 22 Feb 2002 16:45:53 -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 167 invoked from network); 22 Feb 2002 16:45:52 -0000 Message-ID: <3C7666B2.F8C6B4F3@apache.org> Date: Fri, 22 Feb 2002 16:41:38 +0100 From: Stefano Mazzocchi X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: XSLT benchmarks: dbonerow References: <200202211107.42742.jacek_ambroziak@yahoo.com> <0ba701c1baf3$8f093890$8501a8c0@TILLER> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Robert Koberg wrote: > > If you look at and evangelize the use of keys you will see performance > increase DRAMATICALLY. Yes, sure, but since most of these optimizations are algorithmical (means that it's possible to write a program that does them for you, as Scott suggested), why in hell should we spend time/effort/energy and brain cells to do something that the XSLT processor should do for us? It's like optimizing SQL: it's a black art. The serious databases optimize the SQL for you, so the serious XSLT prcessors should optimize the XSLT for you. At least, that's how I see it. -- Stefano Mazzocchi One must still have chaos in oneself to be able to give birth to a dancing star. Friedrich Nietzsche -------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org