On 3/5/06, Remy Maucherat <[EMAIL PROTECTED]> wrote: > > I also don't see any need to have zillions of JSPs filled with template > text, especially if you're willing to take a small performance hit > (there's that thing called dynamic includes which could be used to > handle large portions of static text).
Well, unfortunately tomcat-dev's role is to implement a servlet container, not to decide how people should use it and how many JSPs or other technologies should the use, or how they should set up their hardware :-) I don't think it's good to target a single use case or set of users - i.e. huge servers, and sites with small enough number of JSPs to fit in memory. > > Many cases would benefit from more control over memory - hosting or > > embedded or sites with lots of jsps or lots of data. Forcing all > > static content in memory is not the best use of the memory. > > There's no other solution really. Any other implementation will perform > bad, due to the very fragmented nature of static text. Apache seems to do ok with serving static text without loading it all in memory :-) And except JSP, I don't know many other templating solution that requires all data to be in memory - of course, not everything is as fast as JSP, but raw speed is not the only concern :-) >> BTW, I am ok with shipping additional presentation technologies with > >> Tomcat, we do not need to give JSP any special treatment anymore. > > > > True, may be better to implement such a thing without all the > > complexity of taglibs, etc. > > > > Well - my home web server has 32M RAM on a 200 Mhz arm ... :-). Of > > course, I don't plan to run jsp on it - but coyote works well enough. > > Did you look at the other presentation layer technologies available, and > how appropriate they would be for your environment ? Suggestions ? I was thinking of something as simple as SSI ( since the code is already there ), I just need to adapt it for coyote. Costin
