Jerry Cheung

@cjbush what directory are you using? The library does [support error code 49/532](https://github.com/ruby-ldap/ruby-net-ldap/blob/master/lib/net/ldap.rb#L350), but the directory has to return it.

@sbutler thanks for reporting this. There are new active maintainers on this project. Would you be interested in submitting a pull request for this?

Do you notice this behavior with other LDAP clients? It would provide another data point to compare against to narrow down whether it's a bug in the library or elsewhere.

@astockwell thanks for the additional data point. Do you have another LDAP client available to confirm this is server side behavior?

@danleyden that's a great idea. Would you be interested in submitting a pull request for this? I'd be happy to review.

:metal:

> I've been viewing the method accessor as sugar and the [] lookup as preferred, standard, safe, "canonical" accessor. When the method accessor isn't as graceful, I don't mind as...

@ccutrer thanks for the pull. I like refactoring for `new_connection` and `use_connection`. Can you elaborate more on your use case for the connect callback? What decorated socket object would you...

> Not a problem. I was just following the instructions from https://github.com/ruby-ldap/ruby-net-ldap/blob/master/Hacking.rdoc Hah, oops. Sorry about that, I didn't see that previously. Great explanation of your reasoning behind the callback....

@ccutrer good point, but your refactoring of `new_connection` is now the only entry point for opening a new socket. Wouldn't it be the same as the callback if we saved...