[jdjlist] RE: Caching

Tue, 04 Mar 2003 13:02:04 -0800

That sounds very interesting.  It actually sounds similar to the sun article I've just come across:
 
 
However, I know there are lots of gotchas and design caveats that are not addressed by this article, including the expired item re-loading from DB and keeping the cache to a certain manageable size.
 
I am especially interested in the distributed cache management scheme you mentioned.  Having duplicate cache contents on all of our production machines is definitely a major problem.  If there is a way to efficiently share memory among the different machines, I am sure many list members will want to know about it.
 
Thanks in advance,
 
Greg
-----Original Message-----
From: James Stauffer [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 04, 2003 11:48 AM
To: jdjlist
Subject: [jdjlist] RE: Caching

We have our own internally developed object cache. It uses a hard cache (can't be GC'ed) extended by a soft reference cache. It also has a cache manager servlet and another servlet to manage the caches across machines.  It mostly only caches objects of the following:
 
public interface CacheAble {
  public int getID();
 
  public String getClassName();
 
  public String getDescriptor();
}
If you are interested I can probably give more design details.

James Stauffer

---
You are currently subscribed to jdjlist as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
http://www.sys-con.com/fusetalk

Reply via email to