qazmlp wrote:
As I understand, we can write LDAP client program in C, Perl, Java etc. I
would like to know whether they all use the same logic of translating into
C code finally(LDAP command line tools or Java -> C) and then send the
LDAP message to the server. I am asking this because, there is a specific
RFC(RFC1823) written only for the C APIs and hence I thought whether each
of the LDAP implementation currently available follow the 'Other
language/tools->C' approach, before sending the LDAP message to the
server.
The "higher level language" does not have to wrap the C API in order to
use the LDAP protocol. All you have to do is abide by the protocol
documents specified by RFC 2251-2256 regarding the encoding of the bits
on the wire (ASN.1/BER) and the behavior of the client. Some APIs take
this approach - Net::LDAP in perl and the Mozilla Java SDK are "native"
in the sense that they do the BER codec in their respective languages
without "dropping down to C". Other APIs take the C approach - Mozilla
perldap and python ldap are mostly just "wrappers" around the Mozilla
LDAP C libs and the OpenLDAP C libs respectively. Tools like swig can
automate the task of wrapping the C API in the language of your choice.
Other than the C API, I don't think there is a standard. Many web
application programmers use JNDI which is sort of a de facto Java
standard since it's "built in" to the JRE.
Could anybody clarify this? Do the LDAP RFCs have a say on this topic?
---
You are currently subscribed to [email protected] as: [EMAIL PROTECTED]
To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the
SUBJECT of the message.
---
You are currently subscribed to [email protected] as: [EMAIL PROTECTED]
To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the
SUBJECT of the message.
