Are these points that need to be considered on the design of the LDAP DAS, and we should think about a pluggable layer that would abstract these behaviors and allow for different implementations. This would allow for people to enable support for different LDAP servers with minimal work .
Thoughts ? PS.: I know Ole have started a design document, but I haven't had a chance to look into it yet, so I'm sorry if I'm just repeating what is there already. On 3/29/07, Quanah Gibson-Mount <[EMAIL PROTECTED]> wrote:
--On Thursday, March 29, 2007 10:43 PM -0500 Ole Ersoy <[EMAIL PROTECTED]> wrote: > Oh - Cool - Do you know how to do it via JNDI by any chance? > > I assume it's similar to how ADS does it... > > I guess we'll just have to make sure the DAS understands various > "Configuration Dialects" > then. Sorry, although we use JNDI, we've not switched to using back-config yet (instead of text configuration files) so it is not something we've played with. :) --Quanah -- Quanah Gibson-Mount Senior Systems Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
-- Luciano Resende http://people.apache.org/~lresende
