michael at stroeder.com
Sat Apr 10 00:10:49 CEST 2004
Jerome Alet wrote:
> I'd prefer my program to ignore the LDAP
> architecture of the particular site, since it must work on
> many different ones.
I can understand this goal (see web2ldap) but...
> I just want my software to deal with a single LDAP server at any
> time, and if for a particular operation python-ldap receives
> informations telling it that another server should be asked for this
> operation instead, then I'd really like python-ldap to do all the
> dirty work automatically for me,
Think about these aspects:
Which bind information (method, username or bind-DN, credentials) to use at
the referred server?
Should the application continue to use the referred server after referral
has been received or switch back to the original server?
(Hint: Think about referrals being knowledge references to other parts of
the DIT vs. your master-slave scenario.)
You can believe me: I already thought about various aspects. I never came up
with some ideas I was really confident it will work in a generic way.
More information about the python-ldap