> Fra: Emmanuel Lécharny [mailto:[email protected]] > Sendt: 23. februar 2016 22:07
... > We have had a discussion about adding a cache in Fortress last october in > Budapest. Bottom line, what would be the best solution would be to have > ApacheDS embedded into Fortress, with a in-memory backend (which we > have in ApacheDS) and use it as a cache. If the element we are looking for is > not present, then we fetch it from the remote server. Another option would > be for the embedded ApacheDS server to be a consumer of the remote > LDAP server : it will not allow any update to be done locally, but will be > informed immediately when such a change is done on the remote server. > > We agreed that there is a bit of work to get this done, but all in all, it's > feasible. We probably have to strip down some of the code in ApacheDS (like > we don't need the JDBM part, nor the Kerberos/DHCP/DNS code), making it > a bit lighter. > Thanks Emmanuel. I forgot that we already had talked about that.
