[re-posting due to poor formatting of my initial message] I haven't dived into the Tomcat solution as much as I'd like to, but one of my concerns about global JSP usage has always been the issue of web server restarts when making updates, or the loss of session info when updating servlets. Using WebSphere 2.03, this has always been a problem. When we make a JSP change we often have to re-start the web server. When we update or add a JavaBean, we always have to. When we replace a Servlet, the server unloads and reloads them all, thus losing our session tracking objects at the same time. Obviously an ISP will not be able to deal with one user's changes having an impact on another user on the same web server in such a way just because they updated a JSP or Bean or Servlet. The situation isn't any less tedious in our own JSP development and maintenance. Does the Tomcat implementation handle all of these issues? Unless it does I still don't see who can adopt this for more than dedicated web server set-up at your general ISP currently only offering Perl on UNIX. Dan -- Daniel Kirkdorffer NACN IS: 425-580-6225 Sr. Consultant, Syllogistics LLC Email: [EMAIL PROTECTED] Web: http://www.syllogistics.com/ =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". Some relevant FAQs on JSP/Servlets can be found at: http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.html http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
