[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: Newbie question
I'll certainly defer to the LDAP heavies here, but it doesn't need to be an
either-or situation.
That is, it's quite practical to implement an LDAP server on an SQL RDBMS,
and such products exist (Oracle, I expect). This is possible since LDAP
defines a set of services that must be made available to clients, and
doesn't talk to the storage issue - which is an implementation factor.
So if that's important to you, then I'd look for a conforming product.
Arnold Shore
Annapolis, MD USA
-----Original Message-----
From: owner-openldap-general@OpenLDAP.org
[mailto:owner-openldap-general@OpenLDAP.org]On Behalf Of Ana Cruz Martín
Sent: Monday, January 29, 2001 6:18 AM
To: openldap-general@OpenLDAP.org
Subject: RV: Newbie question
Hi everybody:
I have a question that may sound too newbie, but I have been searching
information about this and I haven't found anything clear.
The thing is that I'm working on local phone directories, accesible via web.
By now, we are using a relational database, but we are thinking of migrating
it to an LDAP directory. The problem is that don't know exactly if it is
possible or even a good idea. Our main doubt is related to the number of
readings vs. writings of the data: we know we have quite a few accesses to
our web, but we usually include a lot of new data on the database everyweek.
Is a good idea using an LDAP directory then?
I hope you can help me. Thanks a lot in advance...
Ana+