Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 98840 invoked from network); 9 Nov 2000 04:34:33 -0000 Received: from msp-65-25-234-27.mn.rr.com (HELO localhost.localdomain) (65.25.234.27) by locus.apache.org with SMTP; 9 Nov 2000 04:34:33 -0000 Received: from localhost (IDENT:nick@localhost [127.0.0.1]) by localhost.localdomain (8.9.3/8.9.3) with ESMTP id WAA28345 for ; Wed, 8 Nov 2000 22:41:30 -0600 Date: Wed, 8 Nov 2000 22:41:30 -0600 (CST) From: Nick Bauman X-Sender: nick@localhost.localdomain To: tomcat-dev@jakarta.apache.org Subject: Re: No revolution today In-Reply-To: <973747650.3a0a35c2db573@hgo1.cs> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Thu, 9 Nov 2000, Henri Gomez wrote: > > It is important that tomcat3 has a design that allows support for > > future > > versions of the servlet API, but if tomcat developers don't want to see > > it > > happen - so be it. When Servlet2.3 will be final and in wide use, there > > is > > nothing that can stop someone from providing the module that supports it > > ( > > not necesarily from apache site ). > > Many of us could live with a bullet proof TC 3.3 with API 2.2/JSP 1.1 for at > least one or two years. Note that many importants sites still use Apache JServ > (API 2.0) and GnuJSP. > I for one, would love to see the 3.x codebase's Session API actually work "as advertised" in a web server farm with a rotator box like BigIP. Right now the Session API in tomcat 3.1 /does not work/ across multiple instances of tomcat in a server farm.