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 40936 invoked from network); 20 Jan 2001 03:36:51 -0000 Received: from scaup.prod.itd.earthlink.net (207.217.121.49) by h31.sny.collab.net with SMTP; 20 Jan 2001 03:36:51 -0000 Received: from SANTANA.bitbull.com (pool-63.49.209.138.troy.grid.net [63.49.209.138]) by scaup.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id TAA02901 for ; Fri, 19 Jan 2001 19:36:56 -0800 (PST) Message-Id: <4.3.2.7.2.20010119223249.0225e908@pop3.demon.co.uk> X-Sender: kief_bitbull@kief.demon.co.uk@pop3.demon.co.uk X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 19 Jan 2001 22:36:44 -0500 To: tomcat-dev@jakarta.apache.org From: Kief Morris Subject: Re: [PROPOSAL] Tomcat 4.0-beta API Change: Security Manager Facades In-Reply-To: <3A68C6E4.A127F7BA@eng.sun.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Craig R. McClanahan typed the following on 02:59 PM 1/19/2001 -0800 >> So what do we need a 4.1 branch for then? > >If we take the action Remy recommends, we won't. I'm +1 for this OK, I understand the motivations for this. When/how do you think the PersistentManager code I submitted last week should be integrated? I hate to put more untried code into 4.0, but I'd really like to see it committed somewhere where people can try it and I can build onto it. I have a number of things I'd like discuss doing with the session classes, like refactoring StandardSession into an abstract class and implementing the locking/request completion stuff we've discussed here. Kief