atom feed10 messages in org.apache.tomcat.devRe: Global caching hack?
FromSent OnAttachments
Alex ChaffeeJun 15, 2000 8:20 pm 
Robin GieseJun 16, 2000 2:13 am 
NachoJun 16, 2000 3:27 am 
Alex ChaffeeJun 16, 2000 6:45 am 
Craig R. McClanahanJun 16, 2000 9:55 am 
Jonathan ReichholdJun 16, 2000 10:05 am 
NachoJun 16, 2000 10:15 am 
Chun, Byung (GEAE, Elano)Jun 16, 2000 10:18 am 
Craig R. McClanahanJun 16, 2000 10:29 am 
Joseph DaneJun 16, 2000 12:45 pm 
Subject:Re: Global caching hack?
From:Jonathan Reichhold (reic@singingfish.com)
Date:Jun 16, 2000 10:05:58 am
List:org.apache.tomcat.dev

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" <rt@digitalkiwi.com> To: <tomc@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