On 6/29/07, Daniel Ouellet <[EMAIL PROTECTED]> wrote:
Almir Karic wrote:
> if you have trully big setups you might wanna look at ldap, from what
> i've heard/read it should perform well under heavy read intensive
> operations.
I always see a lots of LDAP talks and some documents on it for many
things including managing multiples users on multiples servers as a way
to make life easier. To be honest. I never set one up yet. Doesn't know
much about it either. Always been on my list of things to learn and
explore. I guess I never came across a very good document that explain
it so well to me with pro/cons to trigger my interest to try it yet.
Lots on the net for sure. It just haven't grab me yet. May be that's the
best things after slice bread and I am missing out. I don't know. May be
if someone have a reference they ever come across that really trigger
their interest and turn them to it, I would love to read it. I would
very much appreciate the pointers to much reading. My ignorance on that
subject always makes me think that it could be done with SQL, what ever
flavor you like, so why yet use an other database LDAP? See my total
dark side to it. (;> I never came across a reason or reading to push me
to learn it and see it as better then other solutions. I am more then
open to be put in the 21th century and learn it however if that's so
blind of me.
http://www.ldapman.org/articles/intro_to_ldap.html IMO good intro to ldap.
if you just want to deploy a not-huge mail server you probably won't
see any advantages of ldap over mysql.
what you can do with ldap (IMO) much better than with mysql is ACL, i
found the 'self' to be pretty nice, example:
access to attrs=userPassword,shadowLastChange
by dn="cn=admin,dc=my,dc=domain" write
by anonymous auth
by self write
by * none
--
almir
