> -----Original Message----- > From: fedora-directory-users-bounces at redhat.com > [mailto:fedora-directory-users-bounces at redhat.com] On Behalf > Of jclowser at unitedmessaging.com > Sent: Monday, June 13, 2005 10:36 AM > To: General discussion list for the Fedora Directory server project. > Subject: Re: Ideas for fds [Auf > Viren gepr?ft] > > Rich Megginson wrote: > > > Frerk.Meyer at Edeka.de wrote: > > > >> Actually there are more kinds of 'groups' in a FDS / Netscape/ Sun > >> LDAP Directory Server than just group entries: > >> > >> 1) Treenodes / Entry DN > >> Every node defines a group of its subnodes and leaves. > >> If a person entries is under some organisation and > organisationunit > >> nodes, it is member of the organisations and organisationalunits. > >> Membership can be deduced from the DN of that entry. Search all > >> person in a subtree are the member of that 'group' > >> > >> > > Right. But then moving an entry from one group to another becomes > > problematic. Even if the server supports the modrdn or > subtree rename > > operation, it can be a problem for apps that expect the > entry DN not > > to change. > > And applications that depend on a particular tree structure > or the format of the dn are a nightmare, because if you are > trying to integrate > 2 of them in the same directory, they probably won't match > up. I prefer to allow entries to be more or less anywhere in They are indeed a nightmare - and this scenario is one of the targets for the FDS virtual views feature - if you can't change the apps, change the dit on the fly...
