@PublicAPI(stability=UNCOMMITTED)

Package org.opends.server.protocols.internal

Contains the implementation for the "internal" connection handler and its associated classes.

See: Description

Interface Summary

Interface	Description
InternalSearchListener	This interface defines the methods that must be implemented by a class that wishes to perform an internal search operation and be notified of matching entries and referrals as they arrive rather than altogether when the search has completed.

Class Summary

Class	Description
InternalClientConnection	This class defines a pseudo-connection object that can be used for performing internal operations.
InternalConnectionHandler	This class defines a Directory Server connection handler that will handle internal "connections".
InternalLDAPInputStream	This class provides an implementation of a java.io.InputStream that can be used to facilitate internal communication with the Directory Server.
InternalLDAPOutputStream	This class provides an implementation of a java.io.OutputStream that can be used to facilitate internal communication with the Directory Server.
InternalLDAPSocket	This class provides an implementation of a java.net.Socket object that can be used to facilitate internal communication with the Directory Server through third-party LDAP APIs that provide the ability to use a custom socket factory when creating connections.
InternalLDAPSocketFactory	This class provides an implementation of a javax.net.SocketFactory object that can be used to create internal LDAP sockets.
InternalSearchOperation	This class defines a subclass of the core search operation that is to be used for internal searches.
Requests	This class contains various methods for creating and manipulating requests.
SearchRequest	Search request implementation.

Package org.opends.server.protocols.internal Description

Contains the implementation for the "internal" connection handler and its associated classes. The internal connection handler is not actually intended for use in communicating with external clients, but rather may be used for performing internal operations invoked by other Directory Server components (e.g., plugins). This internal protocol implementation is specifically designed to allow these kinds of internal operations to be processed efficiently and in potentially the same way as if they had been received from a remote client using some other protocol (e.g., LDAP).