Hi, >content, if performance gain is significant, it would be the right way
That's a big if that I am far from convinced is true. >ease of use. Having to install Apache and Tomcat obviously is not a You don't have to, and in most cases the benefit is negligible. Tomcat standalone is sufficient for many servlet/JSP apps, including those with high load and significant static content. >adding this seems to be the right thing to do. However, this is based >on the assumption that moving to new io is an easy thing to switch over >in Tomcat, and no other better alternative to improve this performance >(except the alternative and this method both improve the performance >greatly, then why not do both). Both those assumptions are wrong. Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
