Hi, >> No to both of your questions. Cookies present minimal overhead anyways: >> if they even show up on your profiler CPU time display, then you've done >> an unbelievable tuning job. > >I am not tuning CPU overhead, I am tuning number of bytes transmitted >for every request. And for network bandwidth with many very small >requests this makes a difference.
I accept the network bandwidth point. If you're using a context XML file packaged with your WAR (only available in tomcat 5 and later), then you can include cookies="false" in your context definition. This is documented in http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/context.html. However, the server will then use URL rewriting, which results in longer URLs, and moreover this doesn't disable cookies altogether, just authentication cookies. Yoav Shapira 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]
