Costin Manolache wrote:
Using less memory and supporting users who don't run tomcat on huge servers is not ridiculous. And 'this is not my use case' is not a valid reason to veto IMO.
We're talking about a very small amount of memory. Webapps which have lots of large JSPs are not small webapps, obviously: they are going to require lots of resources anyway. Using straight classes is quite efficient besides the small initial memory cost.
How are JSPs GC friendly ??? By keeping all strings referenced by the class, so they can't be GC until the webapp is unloaded ?
Trying to argue with you is a complete waste of time. I meant, obviously, that this makes it very easy to not generate a ton of garbage objects per invocation.
I think it is perfectly possible to compile JSPs in a different way - the current compilation is not the only solution or only way to generate java from the jsps.
Whatever you say.
I also agree with you that JSPs are complex enough that messing with the code generation is too dangerous - I wouldn't touch it, but if some people have patches, we should consider them.
They should bring a demonstrably useful benefit. This proposed redesign is only useful thanks to Sun's VM memory management.
Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
