Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 74386 invoked by uid 500); 7 Feb 2002 11:42: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 74375 invoked from network); 7 Feb 2002 11:42:52 -0000 Message-ID: <3C62682F.16843215@apache.org> Date: Thu, 07 Feb 2002 12:42:39 +0100 From: Stefano Mazzocchi X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Apache Cocoon Subject: [vote] move tree-processor in the main trunk Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Ok, sitemap code generation is getting slower every day and is likely to become worse as we add more bugfixes and error generation. Clearly, developping on cocoon with 20 seconds delays between changes is a nightmare and would scare people away instantly. Now that we have a functional interpreted sitemap engine, I suggest we move this on the main trunk and keep improving on it from there. Also, I would like to propose a name change: TreeProcessor isn't exactly self-explanatory as a 'sitemap interpreter'. Moreover, I'd love to be able to decide what to use (interpreted or compiled) from cocoon.xconf.... or, in case the treeprocessor ends up faster all the time, simply blast the compiled version and get rid of that stupid javac! What do you think? -- 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