Bad LDAP coding, bad Application, but....maybe the LDAP Implementation?
It is true that Poorly written LDAP[?] code can really affect your Portal, Suretec have seen it a few times:
A programmer who hadn't had much exposure to LDAP decided it best to do a base level search, for example, usingldapsearch:
he retrieved *everything*, then did all the searching/filtering etc. locally in the client! What's the point of a Directory Server!?!
Our partners Symas have also talked about similar encounters, mainly with Sendmail.
It all comes down to the level of LDAP understanding a programmer has.
Or could it actually be the Directory Server implementation, namely Oracle Internet Directory (OID)?
I know OpenLDAP wouldn't slow an app down like this, because it's very fast..very very fast
A programmer who hadn't had much exposure to LDAP decided it best to do a base level search, for example, using
CODE:
ldapsearch -x -b 'dc=suretecsystems,dc=com' '(objectclass=*)' -H ldap[?]://127.0.0.1
he retrieved *everything*, then did all the searching/filtering etc. locally in the client! What's the point of a Directory Server!?!
Our partners Symas have also talked about similar encounters, mainly with Sendmail.
It all comes down to the level of LDAP understanding a programmer has.
Or could it actually be the Directory Server implementation, namely Oracle Internet Directory (OID)?
I know OpenLDAP wouldn't slow an app down like this, because it's very fast..very very fast
Trackbacks
The Suretec Blog on : OpenLDAP Weekly News Issue 6
Show preview
Welcome to the sixth issue of OpenLDAP Weekly News (OWN), the unofficial weekly newsletter for the OpenLDAP community.
This will be released every Sunday (or thereabouts), covering the latest goings on in and around the OpenLDAP community.
Summary:
Comments
Display comments as Linear | Threaded
James on :
James on :
Gavin Henry on :
This is bound to be more efficient than the client side programmer.
James on :
Gavin Henry on :