That's true, I had forgotten that. Too used to tomcat I guess. Btw, as an FYI, Oracle's web server is a Apache 1.3.x w/a modified version of JSERV. It supports jsp's via a Servlet (I think, not sure), but it's still using the JSERV level of the APJ protocol. The biggest problem is with that protocol, opening and closing sockets as it talks to the JVM ends up with tons of sockets in a close wait state. On Unixware this is a problem.
--mikej -=----- mike jackson [EMAIL PROTECTED] -----Original Message----- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 8:58 AM To: Tomcat Users List Subject: RE: Going Live Howdy, >one file. The container will extract that and build the file system >structures required. There's much less chance for error. Just one note: the container is not required to do this and may keep your war file packed. This is one reasons why you should use ServletContext's getResource()/getResourceAsStream() instead of pure File-based APIs in your web applications. Yoav Shapira Millennium ChemInformatics 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
