[
https://issues.apache.org/jira/browse/FC-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14202088#comment-14202088
]
Emmanuel Lecharny commented on FC-42:
-------------------------------------
There is one good reason we would like to use one single connection for a whole
operation.
Assuming that during this operation, we are likely to update the server more
than once, we might want to enforce some kind of atomicity on the server (ie,
either the operation finishes successfully, or fails, but in any case, the ldap
server content is clean in both cases). If the LDAP server supports
transactions (and OpenLDAP does, so will ApacheDS sooner or later), then it
will be possible to enforce data integrity across one single connection,
something impossible to enforce if we use many connections...
Thoughts ?
> Avoid pulling a new connection from the LDAP connection pool
> ------------------------------------------------------------
>
> Key: FC-42
> URL: https://issues.apache.org/jira/browse/FC-42
> Project: FORTRESS-CORE
> Issue Type: Improvement
> Affects Versions: 1.0.0-RC39
> Reporter: Emmanuel Lecharny
> Fix For: 1.0.0-RC40
>
>
> Atm, everytime we want to send a request to the LDAP server, we are acquiring
> a connection from the LDAP pool of connections. It's quite expensive, as each
> connection has to be rebind everytime we push it back, and we do a validation
> (thus a read) everytime we ask back a connection.
> If we were to pass the connection we picked in the first call to all the
> methods, we would save those costly Bind and check.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
