[Tickets #2371] supporting contact lists in LDAP backend

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=2371
-----------------------------------------------------------------------
 Ticket             | 2371
 Updated By         | Chuck Hagenbuch <chuck at horde.org>
 Summary            | supporting contact lists in LDAP backend
 Queue              | Turba
 Version            | 2.0.3-RC1
-State              | New
+State              | Feedback
 Priority           | 2. Medium
 Type               | Enhancement
 Owners             | 
-----------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2005-08-03 14:44) wrote:

Is the groupOfNames objectclass standardized enough to hardcode like this?

If so, I don't mind the patch in general. I'd like to see more comments for
each change block, and to see it cleaned up to follow CODING_STANDARDS. You
should also provide a patch for sources.php.dist, instead of a new
sources.php file.

Also, the change to Object.php is duplicative, and why the change to
browse.php?

If all the changes were localized to the LDAP driver I'd feel better about
it. Would using this method completely replace the existing method for
storing groups in LDAP? What kinds of ids do other clients store in a
groupOfNames object? I'm guessing we couldn't store ids for non-LDAP
contacts this way, which we can do the current way. Would it be possible to
introdue groupOfNames as a different kind of group, or as a read-only
interpretation of what's on the LDAP server already?