Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Message-ID: <004a01bfd7b5$31934250$3e00000a@sttln1.wa.home.com>
From: "Jonathan Reichhold" <reichhold@singingfish.com>
To: <tomcat-dev@jakarta.apache.org>
References: <001901bfd773$291adb20$6500a8c0@internal.digitalkiwi.com>
Subject: Re: Global caching hack?
Date: Fri, 16 Jun 2000 10:06:20 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

What about an RMI object that can be accessed from each servlet/JSP? This
way you have one cache which is available from multiple JVM's and contexts
and you can keep the pool to a single instance?  Not sure of the symantics
of the JSP page (may need to use a bean), but why not try it?  Does anyone
have any experience that would show that this would be a bad thing to do?
It seems to me that this is a really powerful technique which isn't used
nearly enough.  Thoughts?

Jonathan
----- Original Message -----
From: "Robin Giese" <rtg@digitalkiwi.com>
To: <tomcat-dev@jakarta.apache.org>
Sent: Friday, June 16, 2000 2:13 AM
Subject: Global caching hack?


> Hi,
>
> I was wondering how I'd be able to hack my own global cache (or rather,
> bunch o' variables) into Tomcat that would be available to all servlets
and
> JSP pages. I'm trying to share an Oracle connection pool (and a couple
> similar, global, very large, non-session dependent objects) to all my
> servlets and JSPs, and I don't want to build a different cache for each
> servlet and JSP page, because it would be an incredible waste of memory.
> Where would be the right place for this kind of hack? Or is there an
> existing facility I could hack up to make it not a complete hack?
(However,
> the objects aren't serializable.)
>
> Thanks,
>
> --robin
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>