[ net-ldap-Feature Requests-23425 ] Ability to leave the connection open
nor...@rubyforge.org
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=634&aid=23425&group_id=143
Category: None
Group: None
>Status: Closed
Priority: 3
Submitted By: Nobody (None)
Assigned to: Nobody (None)
Summary: Ability to leave the connection open
Initial Comment:
I'd like to be able to leave an LDAP connection open.
I know the library doesn't want me to, but I would like to be able to decide what to do with my own network connections.
In some cases, leaving the ldap connection open makes writing my application a lot easier, for example, where I want to only use one ldap connection for each request to a rails app, but don't want to have to wrap the whole request in an LDAP.open. Or even to have an ldap connection pool, as you would a mysql connection pool.
I would suggest:
1. Altering LDAP.open to open the connection and leave it open if a block is not given.
2. Adding a close method to close connections.
----------------------------------------------------------------------
>Comment By: Austin Ziegler (austin)
Date: 2011-07-12 12:27
Message:
Moved to GitHub Issues: https://github.com/ruby-ldap/ruby-net-ldap/issues/11
----------------------------------------------------------------------
Comment By: Austin Ziegler (austin)
Date: 2010-09-25 00:01
Message:
This is not currently planned and I'm not sure it's generally a good idea based on my understanding of how LDAP is supposed to work.
I understand your request for a connection pool, but either doing that or just keeping the connection open introduces a lot of extra code when we do operations to ensure that the currently opened connection is still valid.
Can you make a stronger case for this feature?
----------------------------------------------------------------------
Comment By: James Hewitt (jamstah)
Date: 2009-01-03 20:54
Message:
Forgot to log in before submitting, I submitted this.
----------------------------------------------------------------------
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=634&aid=23425&group_id=143