The following is my understanding: - LDAP server encodes the response always in the ASN.1 format - LDAP client program (E.g. openLDAP client that is released by the SUN) decodes the ASN.1 encoded response data - LDAP client program, returns the response in the format as it is entered in the LDAP entries (String, number, true/false etc.) to our client program(Program-1).
Is that correct? We have a requirement in our client program(Program-1) to read the LDAP response and encode it in the ASN.1 format and send to an other process(Program-2) via the IPC messaging. As you can notice now, the ASN.1 encoding/decoding happens at two places. 1. encode in LDAP server and decode in LDAP client program 2. encode in our client program(Program-1) and decode in the other program(Program-2). Here are my questions: Q1. I would like to know whether we can avoid the 'LDAP client' implementation to skip the decoding part, so that I can reuse the already encoded response while sending the IPC messaging. I could see an API 'ldap_enable_translation()' in the Solaris man pages. Is this meant for that purpose? Q2. The complete LDAP response is sent as an IPC, in the ASN.1 encoded format. Is there a better alternative to this? --- 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.
