Various modules of the ApacheDS manage their own caching systems which are generally simple HashMap based implementations. The problem with this approach is that there is no central configuration and management (on size and object lifetime) for these caches.
Next version of ApacheDS needs a central, unified caching solution. This solution can be based on an existing caching solution or a custom one. In order to get prepared for this change some information needs to be gathered:
- List all parts of the ApacheDS code that use custom caching and specify exactly for what reason they use it.
- Do research on caching system implementation in network servers.
- Do research on available caching systems and also consider custom implementation (or abstracting any caching solution).