Glenn Nielsen at [EMAIL PROTECTED] wrote:
>
> Hmm. I wonder how much optimization is needed in the generated byte code for
> something that will get profiled and optimized to native opcodes by HotSpot
> server. Of course things other than Jasper, like Ant, might want to use it
> with a great deal of optimization. Inclusion/use of the optimization should
> be optional. I would rather have a small footprint fast JSP java source
> compile and let HotSpot server do the profiling and optimization.
Now, I didn't believe it myself until I got the proof, but, IT SEEMS, that
with HotSpot interpreting something like JSPs is actually FASTER than
compiling them...
It was applied to an XSP derivate by some Italian weirdos, and maybe Gianugo
can enlighten us on what he found out... Gianugo?
Pier
- Re: sun.tools.javac.Main will be removed from... Christopher Cain
- Re: sun.tools.javac.Main will be removed from... Pier P. Fumagalli
- Re: sun.tools.javac.Main will be removed from JDK... Craig R. McClanahan
- Re: sun.tools.javac.Main will be removed from... Pier P. Fumagalli
- Re: sun.tools.javac.Main will be removed ... Christopher Cain
- Re: sun.tools.javac.Main will be remo... Pier P. Fumagalli
- Re: sun.tools.javac.Main will be... Christopher Cain
- Re: sun.tools.javac.Main wil... Pier P. Fumagalli
- Compiler API Features [Was: sun.tools... Craig R. McClanahan
- Re: Compiler API Features [Was: ... Glenn Nielsen
- Re: Compiler API Features [W... Pier P. Fumagalli
- Re: Compiler API Features [Was: ... Pier P. Fumagalli
- Re: sun.tools.javac.Main will be removed from JDK1.4 Paul Speed
- Re: sun.tools.javac.Main will be removed from JDK... Craig R. McClanahan
- Re: sun.tools.javac.Main will be removed from JDK1.4 Christopher Cain
