[Date Prev][Date Next]
Re: (ITS#3756) dyngroup,dynlist merge
--On Monday, November 28, 2005 11:39 AM +0100 Pierangelo Masarati
>> Full_Name: Quanah Gibson-Mount
>> Version: OpenLDAP HEAD
>> OS: Solaris 8
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (188.8.131.52)
>> It would make the most sense for the dyngroup and dynlist overlays to be
>> into a single overlay (probably just called dyngroup) rather than
>> appearing as
>> seperate overlays, since dynlist is really just an extension of the
>> group functionality introduced by dyngroup.
> Added to HEAD; the overlap is not yet complete because I realize right now
> that dyngroup can map multiple pairs group/member types, while dynlist
> allows just one. There's a slight change in behavior when implementing
> dynamic groups: in the early implementation, the <attrs> portion of the
> URI was simply ignored, while now it must be absent (this is dictated by
> "paranoid" checks in backend_group() which I totally agree upon).
> Unless the multiple group/member feature is deemed essential, I'd consider
> this ITS fulfilled.
Fine by me, I only plan to use one way of doing groups (I assume you mean
multiple groups are possible, but only with one defined method).
Principal Software Developer
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html