Skip to main content

Blog Archive for jhook during January 2007

Often when you are looking at caching 'requirements', you have a couple things to think about: Allowable duration (only guarantee the object/data for 30 or 20 minutes at most) Optimized memory use (don't cache too much) No where do requirements base themselves on 'do not store more than 200 widgets at once in memory'. So why do these caching implementations work that way? Granted, there's...
Working with Hibernate and attempting to wrap caching services elsewhere in one of our applications, I'm concerned with the way these caching frameworks handle expiration. If you have many different types of domain artifacts that you want to cache with a given lifespan, how come all of these caching frameworks (EHCache, OSCache, etc) don't automatically clean up the memory? It becomes a game of...