LDAP with indefinite length encoded BER

[NOasto...@lineone.net]

I am doing some development that will involve writing some of my own
low-level rotines to send and receive LDAP messages to eDirectory.

I am using a very targetted subset of LDAP so for effieiency (and other)
reasons, I want to avoid using any generic third party libraries to encode
the LDAP and the BER sent to eDirectory (and decode the response). As I am
dealing with a subset, I want to only implement the minimum possible for
first release.

But one specific thing I need to know is how eDirectory handles the
indefinite form of length encoding of the BER. RFC 2251 (LDAP v3) says
"Only the definite form of length encoding will be used." but as this just
is an RFC, some Directory Servers deviate from it. So :

1. How would eDirectory react if I send an LDAP request with indefinite
length encoding?

2....and does eDirectory expect large binaries (jpeg or certs) to be
definite length encoded?

3. Does eDirectory ever send LDAP Responses that include any indefinite
length encoding?

4. ...again, with large binaries, are these always definite length encoded?

I appreciate that this is low level and a little obscure for most people so
any help would be very much appreciated.

Thanks in advance.
Andrew Storer

[Richard Beels [SysOp]]

since this is a programming questions, please go ask in the develp
support forums at developer-forums.novell.com...

--
Cheers!
Richard Beels
http://www.dsi-consulting.com
Collaboration without complication