This class has been deprecated because there are two competing
specifications that can affect the visibility of entries with the
ldapSubEntry object class: RFC 3672 and
draft-ietf-lddup-subentry. This class implements support for the
latter and remains fully functional, but you should use either
the RFC3672SubentriesRequestControl class or the
DraftLDUPSubentriesRequestControl class to avoid
ambiguity.
The use of auto-reconnect is strongly discouraged because it
is inherently fragile and can only work under very limited
circumstances. It is strongly recommended that a connection
pool be used instead of the auto-reconnect option, even in
cases where only a single connection is desired.
The use of auto-reconnect is strongly discouraged because it
is inherently fragile and can only work under very limited
circumstances. It is strongly recommended that a connection
pool be used instead of the auto-reconnect option, even in
cases where only a single connection is desired.
The use of interactive transactions is strongly discouraged
because it can create conditions which are prone to deadlocks
between operations that may significantly affect performance
and will result in the cancellation of one or both operations.
The use of interactive transactions is strongly discouraged
because it can create conditions which are prone to deadlocks
between operations that may significantly affect performance
and will result in the cancellation of one or both operations.