directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn McKinney (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FC-42) Avoid pulling a new connection from the LDAP connection pool
Date Fri, 07 Nov 2014 15:29:33 GMT

    [ https://issues.apache.org/jira/browse/FC-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14202157#comment-14202157
] 

Shawn McKinney commented on FC-42:
----------------------------------

Agreed - we'll put it on the roadmap and target 1Q 2015 for implementation.  This has been
on my wish list for a long time.  

There will be changes both to fortress core and apache ldap api.  The core needs to pass connection
handle for atomic updates. Ldap api will need to support the extended operations for transaction
support.

> 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)

Mime
View raw message