On 4/3/2024 10:22 AM, Howard Chu wrote:
> Jordan Brown wrote:
>> Is there even a straightforward way in the protocol to get type information?
>> If the protocol won't tell you, a client library can't tell you.
> Any client can retrieve the schema definition of any schema element using an
> LDAP
Jordan Brown wrote:
> Is there even a straightforward way in the protocol to get type information?
> If the protocol won't tell you, a client library can't tell you.
Any client can retrieve the schema definition of any schema element using an
LDAP Search request.
--
-- Howard Chu
CTO,
Is there even a straightforward way in the protocol to get type
information? If the protocol won't tell you, a client library can't
tell you.
--
Jordan Brown, Oracle ZFS Storage Appliance, Oracle Solaris
On Wed, Apr 03, 2024 at 02:08:15PM +0100, Graham Leggett wrote:
> On 03 Apr 2024, at 13:03, Ondřej Kuzník wrote:
>
>>> This has been historically vague - first off, what happens if an
>>> attempt is made to call ldap_get_values() on binary data, do you get
>>> an error, or garbage data? The
On 03 Apr 2024, at 13:03, Ondřej Kuzník wrote:
>> This has been historically vague - first off, what happens if an
>> attempt is made to call ldap_get_values() on binary data, do you get
>> an error, or garbage data? The source isn't giving me a clear answer.
>
> Hi Graham,
> in this case
On Wed, Apr 03, 2024 at 10:55:26AM +0100, Graham Leggett wrote:
> Hi all,
>
> Looking back in time to the definitions of ldap_get_values() and
> ldap_get_values_len(), we are told that "If the attribute values are
> binary in nature, and thus not suitable to be returned as an array of
> char *'s,
Hi all,
Looking back in time to the definitions of ldap_get_values() and
ldap_get_values_len(), we are told that "If the attribute values are binary in
nature, and thus not suitable to be returned as an array of char *'s, the
ldap_get_values_len() routine can be used instead."
This has been
