OSCache is a high performance J2EE caching solution that can cache portions of JSP pages, entire HTTP responses (including dynamically generated images), and arbitrary Java objects. It can provide your J2EE application with huge performance gains and graceful error tolerance (e.g., in the event of a DB failure, cached content is served).
|Tags||Software Development Libraries Java Libraries|
Release Notes: CRON expressions to expire content at specific dates and/or times. Pluggable EntryRefreshPolicy. Reduced memory consumption. Faster disk persistence. DiskPersistenceListener deadlocks are avoided if a process has no rights to delete the cache file. There is a new JSP tag _addgroups_, and an interface to get a list of the cache event listeners. The commons collection dependency has been removed. Java 1.3 support has been dropped.
Release Notes: Preserves more HTTP headers, e.g. the expires header. Custom cache key generation by subclassing CacheFilter or by implementing a special interface. Custom cache groups generation by subclassing CacheFilter or by implementing a special interface. Support for GZip filters in the filter chain. Avoids session creation for application scope pages. Multiple matching cache filters won't dead-lock the response anymore. The cache won't be served the same response twice before the client begins to cache it anymore.
Release Notes: This release updates the jgroups jar and configuration, updates the documentation, adds a HashDiskPersistenceListner that hashes file names in order to eliminate nasty characters and overly long names, and adds a property, cache.persistence.overflow.only, that allows cache entries to only be persisted when the memory capacity has been exceeded.
Release Notes: Many bugfixes were made and at least one new feature was added. The cache can now be configured to persist to disk only once the memory capacity has been expended.
Release Notes: There are many improvements over the 1.7.5 release. Some of the key new features include support for grouping of cache entries, entries or groups can now be flushed according to cron expressions, and caches can be distributed across a cluster. The cache configuration has been improved, the documentation has been overhauled, and many bugs have been fixed.