I think there is also a referral chaining control out there somewhere or at least some discussion about it. With referrals you still have to chase the referral: one server tells you that you have to contact another server. With this chaining control the original server you contacted (foo) will go out and do the search for the client on bar server. The results are returned to your client as if all the entries came from foo server.
I guess this is the silver bullet that you're looking for. But some clients like JNDI can automatically chase referrals I think (don't quote me here) so your client code which uses it does not have to have this logic. So Stefan's remarks below are right on the money. In addition just check to see if JNDI can do automatic referral chasing for you. Alex On 10/11/07, Stefan Zoerner <[EMAIL PROTECTED]> wrote: > > The search term "referral" should help. It is a general LDAP concept for > the requirement you describe, and it is supported (among others) by > ApacheDS. > > See for instance here for a very brief explanation > http://ldapadministrator.com/resources/english/help/la331/ch05s05.html > or give Google a try (so did I for the link above). > > Greetings from Nuremberg, > Stefan > >
