Hi everyone, I actually ran into this when fixing the connection leaks. I realized it was probably building in too many assumptions, but I created and held onto the LdapCtxFactory in redback's LdapConnection for a very specific reason: connection pooling. The sun JNDI ldap implementation can pool connections sharing the same credentials *and config options* as long as they are created from the same LdapCtxFactory.
http://download.oracle.com/javase/jndi/tutorial/ldap/connect/pool.html Brent On Wed, Aug 24, 2011 at 8:57 AM, Wendy Smoak <[email protected]> wrote: > On Wed, Aug 24, 2011 at 2:45 AM, Deng Ching <[email protected]> wrote: > > > We're planning to use EhCache for this so we can also set a TTL > > (time-to-live) for the cached objects. A password change done from the > > webapp would flush the user in the cache. > > If you're using LDAP, would users be doing password changes from the > webapp? > > Making that TTL configurable by the admin would be good, then they can > trade off between extra calls to LDAP and 'how come my new password > doesn't work?'. > > -- > Wendy >
