« Return to Thread: Re: 301 permanent redirects in Apache + Tomcat using mod_jk (solved partly)

Re: 301 permanent redirects in Apache + Tomcat using mod_jk (solved partly)

by Bugzilla from fgaliegue@gmail.com :: Rate this Message:

Reply to Author | View in Thread

2008/4/12, Christopher Schultz <chris@...>:

> -----BEGIN PGP SIGNED MESSAGE-----
>  Hash: SHA1
>
>  Francis,
>
>  Francis Galiegue wrote:
>  | Apache is much better at serving static content...
>
>  To be fair, Apache httpd and Tomcat are about equal. But, if you are
>  already using Apache httpd, you may as well have it serve the static
>  content instead of forwarding such requests to Tomcat.
>
>  Sorry to pick nits, but the fallacy that Tomcat sucks as a static
>  content server just needs to die.
>

Well, the performance tests we did (Tomcat 5.0.x/Coyote vs Apache
2.0.x/AJP13/Tomcat 5.0.x) surely didn't account for it being a
"fallacy". I don't know whether this has changed in 5.5.x/6.x, but
Coyote doesn't know about mod_expires and keepalive, for one. And that
makes a huge difference.

--
Francis Galiegue, fgaliegue@...
"When it comes to performance, weight is everything" - Tiff Needell

---------------------------------------------------------------------
To start a new topic, e-mail: users@...
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

 « Return to Thread: Re: 301 permanent redirects in Apache + Tomcat using mod_jk (solved partly)