We try to always use apache for static content and tomcat for
application content.
The only issues we had are when the static content needs to be protect
in someway.
As for speed there is only a small hit serving the static content in
tomcat as opposed to apache.
Phil
Steve O'Hara wrote:
Some nice anecdotal evidence/advice, thanks a lot.
I've got a follow-on question - does anyone have any experience of the
benefits (if there are any) of splitting the delivery of application
pages between static and servlet i.e. have Apache/IIS serve the static
pages and Tomcat/Resin/Jetty the servlets?
I promise to get back on topic soon....
Thanks,
Steve
-----Original Message-----
From:
[EMAIL PROTECTED]
.org
[mailto:[EMAIL PROTECTED]
a.apache.org] On Behalf Of Steve O'Hara
Sent: 01 October 2006 09:26
To: Velocity Users List
Subject: Best Servlet Container
Forgive the slightly off-topic request, but I'm wondering if anyone has
any experience of performance comparisons of all the myriad of servlet
containers out there?
To start the ball rolling, I can safely say that the Oracle App server
is a real dog in comparison to Tomcat but it does have some nice wizzy
monitoring tools (perhaps that's why it's so slow).
I'd like to to know what people's experiences are with Jboss, geronimo,
Webspehere, Jetty etc.
Thanks,
Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
