You're basically rigth. LDAP is optimized for "read many, write few" while DB's are usually optimized for writing. It all depends on the configuration. You can get longer search-time from a misconfigured LDAP server than an optimized MySQL. I once transfered 24000 customers from MySQL to LDAP and the searchtimes were only slightly better on LDAP but when we threw in some indexes it was "much" better.
Another reason for LDAP is the possibility of replication, or delegation of data between servers (and/or operators). If you want to read more about ldap (and have som extra cash :-) you should get the "understanding and deploying ldap directories" from macmillan technical publishing. It's boring, but thorough :-) I would guess there is a lot of online docs available also. Third reason: Clients can connect directly to your LDAP directory and fetch data, f.instance Outlook or any app with LDAP support. Just my own opinions ;-) -Jørg "Paul Meagher" <[EMAIL PROTECTED]> wrote in message 003201c14c4e$07511940$6c35de18@dvore">news:003201c14c4e$07511940$6c35de18@dvore... > I was wondering if someone could tell me what the advantages are of storing > contact info in an LDAP repository are over storing it in, say, a MySQL > repository. > > I am thinking it is mostly a speed and scalability issue - if I have a > million people in an LDAP repository and need to find someone in it the > search time will be alot faster using LDAP than MySQL. Is this correct? > > Is there any other reason to use LDAP over MySQL that I am missing out on > here? > > Regards, > Paul Meagher > > -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
