on 5/16/01 3:28 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> And I tried to explain: the xslt transformation is not significant
> compared with the javac compilation ( it may add 5-10% extra )
"may"? Do you have empirical evidence of that or did you pull that out of
your ass?
>, and may
> end up saving the javac in some cases - which would be a significant speed
> improvement.
Ah. Something else you pulled out of your ass.
> And I also tried to explain: JSP doens't take more resources, a particular
> implementation ( generator ) may take more resources.
Once again, you don't listen very well. I'm not talking about JSP taking
more resources, I'm talking about Jasper taking more resources. In case you
missed it, Xalan is not a lightweight piece of Java code.
> The current
> java-only generator will still be available, there are many ways to
> compile the JSP page - and xslt has some benefits you can't get otherwise.
Oh, so now you are going to support both generators? You are so amazing!
> Generating code is supposed to be resource intensive if you expect
> reasonable runtime performance
Is it supposed to be more intensive than it currently is? You are talking
about slowing things down at least another 5-10%...I'm sure your users will
really love that.
-jon
--
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/ymtd/ymtd.html>
