Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
From: "Peter Guyatt" <pguyatt@telesoft-technologies.com>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Subject: RE: Accessing objects with any servlets,
 where the object is already pre-created
Date: Tue, 7 Oct 2003 14:00:25 +0100
Message-ID: <IIEDKFJNELHIHEMPNDGKCELOCHAA.pguyatt@telesoft-technologies.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <00f101c38d9c$119f1a00$6600a8c0@temple>

Hi there,

It will be a direct reference

thanks

Pete

-----Original Message-----
From: Vidar Langberget [mailto:vidar@langberget.com]
Sent: 08 October 2003 14:00
To: Tomcat Users List
Subject: Re: Accessing objects with any servlets, where the object is
already pre-created


I understand that you can't put every object you want to cache in the
servletcontext, and a holder/wrapper object is needed. But you still need to
call servletContext.getAttribute() once for every request. The question is:
Does it matter performance-wise if the objects you store in the
servletContext are large or small. Ie, when you have the following code:

CacheManager cm = (CacheManager)servletContext.getAttribute("cache"):
FineObj fo = (FineObj)cm.getObject(key);
..

Is cm object getting a reference to the cache attribute(fast), or a copy of
the object stored there(slow)?

Sorry for not making my question clearer.

regards,

Vidar


----- Original Message -----
From: "Tim Funk" <funkman@joedog.org>

> The easy workaround is not store *many* objects into the servletContext
but
> to store a "holder object" into the servletContext.
>
> Rehashing is a non-issue if at initialization time all the information is
> loaded into the servletContext. If not future writes are done into the
> servlet context, then no rehashing is done.
>
> In fact, you can have one object in your servletContext which holds ALL of
> your data. Then you have full control of the hashing issues and don't need
to
> worry about excessive calls to (CAST)servletContext.getAttribute() or
worry
> about static variables.
>


---------------------------------------------------------------------
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