Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 77368 invoked from network); 4 Feb 2003 03:59:10 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 4 Feb 2003 03:59:10 -0000 Received: (qmail 15718 invoked by uid 97); 4 Feb 2003 04:00:46 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org Received: (qmail 15711 invoked from network); 4 Feb 2003 04:00:46 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 4 Feb 2003 04:00:46 -0000 Received: (qmail 73563 invoked by uid 500); 4 Feb 2003 03:58:16 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 73528 invoked from network); 4 Feb 2003 03:58:16 -0000 Received: from icarus.apache.org (208.185.179.13) by daedalus.apache.org with SMTP; 4 Feb 2003 03:58:16 -0000 Received: (qmail 67395 invoked by uid 1059); 4 Feb 2003 03:58:14 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 4 Feb 2003 03:58:14 -0000 Date: Mon, 3 Feb 2003 19:58:14 -0800 (PST) From: "Craig R. McClanahan" To: Tomcat Users List Subject: Re: more about custam tag life cycle In-Reply-To: <3E3EEA56.4040908@ptc.com> Message-ID: <20030203195348.M58880@icarus.apache.org> References: <66337F04F2A1E440BF87F2080B5F537001481DDB@madison.dc.Blackboard.com> <1044295929.1766.224.camel@desenv1.ritterdosreis.br> <044901c2cbb6$8f07e1a0$01000001@Will> <1044153529.2046.2.camel@linux.local> <3E3EEA56.4040908@ptc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Mon, 3 Feb 2003, Erik Price wrote: > Date: Mon, 03 Feb 2003 17:16:54 -0500 > From: Erik Price > Reply-To: Tomcat Users List > To: Tomcat Users List > Subject: Re: more about custam tag life cycle > > > > Joe Tomcat wrote: > > arguments. Object pooling is deprecated, except for expensive objects > > like db connections. > > Are you saying that in general, object pooling is deprecated? In other > words, it's always a bad idea, with the exception of DataSource type pools? > All generalizations are inherently false, including this one :-). There are not very many absolutes in programming -- if object pooling makes your application run faster, by all means use it. If it doesn't make your application faster, then don't bother with it. If you're into the Extreme Programming (XP) approach to iterative development, you will probably implement things without object pooling first (because it's simpler), and only migrate to object pooling if (a) the object creation/GC of this particular kind of object shows up as a performance hotspot in your analyzer runs, and (b) using an object pool actually helps. That being said, you do not really have any choice about whether to design custom tag classes to support being pooled or not. The JSP spec requires you to obey the rules if you want to guarantee portability to all containers. > > Erik Craig > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org