> Lo, Frank. You really don't lose anything. You just gain a choice. > There is a lot more to be said on this, but you probably would know > everything on this anyway, so I will leave it at that.
That's not strictly true though Jack (neither your premise that you don't lose anything or that I know everything about this, I almost certainly don't!)...
In some environments, as I'm sure you know and probably have even dealt with, you have a bunch of web servers in front of a bunch of app servers. The web servers serve static content like images, stylesheets and usually server-side includes, things like that, while the app server handles JSPs and actual server-side (servlet) code.
Putting everything under WEB-INF removes this choice because every request has to be routed to your app servers now. In larger scenarios, the whole point of the web servers (well, most of the point anyway) is to offload that work from the app servers and gain efficiency. Division of labor and all that jazz. :)
I'd certainly agree that if a particular situation doesn't call for such a distributed environment in the first place, than it's a moot point, and what you suggest certainly has some benefits. But if that's not the case, or if it some day might not be the case (i.e., your app might have to scale into such an environment), then it could become an issue and people should be aware of it before they make their decision.
I also don't know what effect this might have in a true distributed environment (i.e., might it be a problem if one request, say for an image, is serviced by one machine, while another services the JSP execuetion itself?). This might never arise, or it might not be a problem at all even if it does, but it could be something for someone to explore is my point.
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com
Dakota Jack wrote:
<snip> On Sat, 29 Jan 2005 17:17:03 -0500, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
One thing worth pointing out about this is that you'll lose the benefit of fronting your app server with a web server... You won't be able to offload the serving of images, stylesheets and such, from the app server to the web server. That's probably not a big problem in many cases where a single server with a decent set of specs can handle the load anyway, but in a more robust "enterprise" environment, your really kind of defeating the purpose of a fleet of web servers in front of a number of app servers.
</snip>
Lo, Frank. You really don't lose anything. You just gain a choice. There is a lot more to be said on this, but you probably would know
everything on this anyway, so I will leave it at that.
Jack
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
