Controlling the Result Queue: The Connection Backlog
When an LDAPConnection object is connected to a server, it has a separate thread listening for incoming messages from the server. The messages are queued for delivery on the basis of the sequential operation number assigned at the time of a request. There may be multiple queues if more than one thread shares a physical connection or if multiple searches (with a batch size of 1) have been requested. The LDAP protocol is asynchronous, and in principle a message can be received at any time, even if no requests have been made. When a client issues a search request that results in a large number of entries being returned, the results may very well be delivered to the client faster than the client ...
Get LDAP Programming with Java™ now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
