Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Date: Wed, 16 Jun 2004 09:34:20 -0500
From: QM <qm300@brandxdev.net>
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
Subject: Re: Multiple requests sharing the same Servlet instance
Message-ID: <20040616143420.GC26902@strange.dreamhost.com>
References: <9C5166762F311146951505C6790A9CF80229BB50@US-VS1.corp.mpi.com>
 <06a501c453ad$7320bef0$bf00a8c0@blraddrcom>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <06a501c453ad$7320bef0$bf00a8c0@blraddrcom>
User-Agent: Mutt/1.3.28i

On Wed, Jun 16, 2004 at 07:53:07PM +0530, Keith Hankin wrote:
: Maybe I'm being dumb, but it seems to me that based upon what I'm hearing,
: there is no benefit of doing Servlet instance pooling since the Servlets
: aren't true objects; they are merely places to put code, since no local
: state is useful.

Depends on how you look at it: they are true objects in that they are
self-referential, and hold some (shareable) state.

Check out the javadoc for the HttpServlet class: by default, the
ServletConfig and some other vars are shared, and you're more than
welcome to share thread-safe objects (such as a logger).  I'd certainly
call those local objects "useful."  =)

-QM

-- 

software  -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org