The referral code is enabled via set_option calls and is currently
processed in relation to a newly created ldap connection. Any further
directory related processing would have to support changing the options
later, or provide extra criteria when selecting a connection to use. But I
agree that, logically, it should be directory scoped.
I'm committing the doc now (directory scoped, to match the code I committed)
and I'll look at making sure the processing addresses that (via merge, etc).
Graham Leggett wrote:
Paul J. Reder wrote:
Now that you ask that question it makes me realize that the better
question is
probably "Should the directives be directory scoped or server scoped?"
The rest
of the util_ldap directives are all server scoped.
The cache related ones are all server scoped, as the cache is server wide.
The SSL related ones are directory and/or server scoped, and it depends
on the underlying toolkit as to whether directory scope works at all.
Don't fall into the trap of thinking all directives have to be handled
the same way. My gut feel is that the referral processing should be
directory scoped, there is no guarantee that the server will only ever
connect to one type of LDAP server at a time, and the admin may want
different processing depending on the application.
Regards,
Graham
--
--
Paul J. Reder
-----------------------------------------------------------
"The strength of the Constitution lies entirely in the determination of each
citizen to defend it. Only if every single citizen feels duty bound to do
his share in this defense are the constitutional rights secure."
-- Albert Einstein
