cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: [vote] move tree-processor in the main trunk
Date Thu, 07 Feb 2002 11:50:13 GMT

Stefano Mazzocchi wrote:
> 
> 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.
> 
+1

> Also, I would like to propose a name change: TreeProcessor isn't exactly
> self-explanatory as a 'sitemap interpreter'.
> 
+1

> 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?
> 
Lets "get rid of that stupid javac!"!

I don't want to maintain two components for the same thing. This will end
up in synchronisation nightmares.

Carsten

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message