search

rwinch / spring-ldap

Apache License 2.0
0 stars 0 forks source link

LDAP-286: Documentation: @Async and Spring-LDAP #117

Open rwinch opened 10 years ago

rwinch commented 10 years ago

Original Reporter: matthewc Environment: Not Specified Version: 1.3.2 Migrated From: https://jira.spring.io//browse/LDAP-286

rwinch commented 10 years ago

marthursson said: I'm not familiar with UnboundId, but from the documentation it appears to support asynchronous LDAP searches re-using the same LDAP connection. Spring LDAP is based on standard Java LDAP/JNDI; and when it comes to protocol features only stuff that's in there is supported by Spring LDAP. This means that async queries as UnboundId describe them are not (and very likely will not be) supported by Spring LDAP.

There is nothing to stop you from executing your queries in parallel, possibly using {{@Async}} - that's a Spring feature completely unrelated to Spring LDAP. Spring LDAP will still continue working the same way however: each Spring LDAP operation will open its own connection to the server and wait synchronously for its response. This means that if you try to execute hundreds of parallel operations, you will require hundreds of LDAP connections to the server, which is not likely to be appreciated by the server administrators.

rwinch commented 10 years ago

matthewc said: That information is useful to know. Thanks.

As for the server admins, I'm one of the server admins, so that part isn't a problem. I was more concerned with having to figure out exactly how large of a connection pool would be needed with a corresponding thread pool for the async calls. It sounds like I'd need them both in the hundreds, if I want to be able to do this.

Thanks.