Re: Default CacheManager strategy

[Tim Veil]

My personal preference would be to enable a cache manager by default. If the optimal/recommended jsecurity configuration includes the use of a cache manger then the default configuration should use a basic cache manager implementation. More advanced users could disable or enhance this configuration.

On Jan 8, 2009, at 8:52 PM, Les Hazlewood wrote:

Now that SoftHashMapCache is available and production quality in that it

won't introduce memory leaks (making it a better option than a

core.

So, now the question is:


automatically by default? or

configure a CacheManager to enable it?

If we think #1 is the preferred, and an end-user does NOT want caching

configure explicitly.  This dummy implementation would satisfy the
CacheManager calls, it would just do nothing.


it.  Something like this in the .ini config:

cacheManager = org.jsecurity.cache.MemoryCacheManager
securityManager.cacheManager = $cacheManager

What does everyone think?

HashtableCache), we can remove the hard dependency on Ehcache in JSecurity 1. Do we enable a MemoryCacheManager (which would use a SoftHashMapCache) 2. Do we disable caching entirely, expecting the end-user to explicitly enabled at all, we could easily provide a NoOpCacheManager that they would If we think #2 is the preferred, it is very easy for the end-user to enable

smime.p7s
Description: S/MIME cryptographic signature