Thank you very much! But if I use several tomcat's instances then I still need some load balancing server, like apache with mod_jk, so why don't use it for content delivery too ? Or do I need to investigate another load balancing mechanism?
Sam Hough wrote: > > [serving static content] > The argument I heard was that Java apps were not able to cope as well with > badly behaved clients (dropped connections etc). Apache httpd probably is > more efficient than Tomcat etc at serving static content. However modern > cheap hardware can almost always shove out more than most connections can > cope with. If you want to manipulate, control access etc to your static > content and your app is in Java I would be tempted to stay with pure Java. > You also have less to worry about which bit of your platform is causing > trouble. Tomcat also has a native plugin that you might want to > investigate... I would guess that careful tuning of what you serve > (compression, cache management) will buy you a lot. > > -- View this message in context: http://www.nabble.com/Wicket-%2B-Hibernate-%2B-Spring-%2B-Terracotta-%2B-Tomcat-%2B-Apache-tf4528720.html#a12935457 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
