> > >After reviewing some of these problems with Apache, my question is, What does using >Apache buy you on the front end. I realize for static content it will help but Slide >and a fairly Java intensive process so where is the benefit? Security? If Apache was >delivering content directly from the file system it would be a benefit, but doesn't >everything have to go through Tomcat anyway. Not trying to be difficult, just curious > >
"Because I can" *chuckle* Really though, Slide is only part of the system I'm building, which includes other Webapps and static content. Apache is primarily the 'middleman.' I have designed the system to reflect security and performance concerns. By putting Apache in front of the components that hold the "business-logic," I can (will) move the tomcat servlet engine to another server. This makes it possible to put in various security measures like a firewall between the two servers, putting the Apache server in a DMZ and the application server on the inside. And though mod_webapp today doesn't support clustering like the ajp13 module, I am sure it will one day. Using Slide's JDBC stores, it may be possible to run Slide on a cluster, at least for the 'viewing' of content (?) HTH Pratik -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
