On Sun, 7 Oct 2001 18:22, Paul Hammant wrote: > Perhaps the ideal web server could take a WAR file (with plenty of > static content) and, at load time, hand the static content to some > sister server that is more tuned to serving static content.
Actually I remember hearing someone mutter that tomcat was going to try to do that with one of the Apache connectors (warp?) or something. Not sure if it does that right now though. > I stand by > my definition, despite performance concerns, that a WAR's root is for > content and WEB-INF is a convenient place to hide conf, libs & classes. And conversely a SAR's root is for content (or application data) and SAR-INF is a convenient place to hide conf, libs & classes ??? > Of course I understand that servers come > with conf and a miriad of jars. My point was simply that stuffing > everything into SAR-INF looks daft and more like an imitation of WAR > files. It is an imitation but not everything will be stuffed into SAR-INF. In fact there is quite a lot of stuff that won't be in a SAR-INF. It is just that up until now we have not differentiated between stuff that is extracted and stuff that is not. Ideally large chunks of james .sar will be extracted while the standard *.bar, *.jar does not need to be extracted. > However, I'm not a do-er in this area of Phoenix, so feel free > to ignore my comments. Technically I can't until you lift your -1 ;) Practically I can't as I have no time atm ;) -- Cheers, Pete -------------------------------------------------- Where ignorance is bliss, 'tis folly to be wise. -------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
