Excepting DNS, is the latest release of OpenLDAP fully asynchronous-capable, even with TLS? Perusing the source code I can't find any obvious places other than DNS where things might block, but it's harder to prove the negative.
I remember many years ago this wasn't the case, and I had to thread the connect phase, but the ChangeLog suggests that things have changed considerably.
William Ahern wrote:
Excepting DNS, is the latest release of OpenLDAP fully asynchronous-capable, even with TLS? Perusing the source code I can't find any obvious places other than DNS where things might block, but it's harder to prove the negative.
I remember many years ago this wasn't the case, and I had to thread the connect phase, but the ChangeLog suggests that things have changed considerably.
Connect has been asynch for years, though an option to configure the connect timeout is a more recent addition.
The only significant thing left that I can think of that's still only synchronous is ldap_sasl_interactive_bind_s(), and I have some plans to fix that.
Hi,
Is there any workaround way by which we will be able to do a DIGEST-MD5 - SASL LDAP bind asynchronously?
Howard: Is there a plan to have an asynchronous ldap_sasl_interactive_bind in the near future? Any time lines for that?
Thanks, Shankar
On Mon, Oct 11, 2010 at 3:06 PM, Howard Chu hyc@symas.com wrote:
William Ahern wrote:
Excepting DNS, is the latest release of OpenLDAP fully asynchronous-capable, even with TLS? Perusing the source code I can't find any obvious places other than DNS where things might block, but it's harder to prove the negative.
I remember many years ago this wasn't the case, and I had to thread the connect phase, but the ChangeLog suggests that things have changed considerably.
Connect has been asynch for years, though an option to configure the connect timeout is a more recent addition.
The only significant thing left that I can think of that's still only synchronous is ldap_sasl_interactive_bind_s(), and I have some plans to fix that. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/
Shankar Anand R wrote:
Hi,
Is there any workaround way by which we will be able to do a DIGEST-MD5 - SASL LDAP bind asynchronously?
Howard: Is there a plan to have an asynchronous ldap_sasl_interactive_bind in the near future? Any time lines for that?
No future plan. It's in CVS as of October 13, so it's already in the past.
Thanks, Shankar
On Mon, Oct 11, 2010 at 3:06 PM, Howard Chu <hyc@symas.com mailto:hyc@symas.com> wrote:
William Ahern wrote: Excepting DNS, is the latest release of OpenLDAP fully asynchronous-capable, even with TLS? Perusing the source code I can't find any obvious places other than DNS where things might block, but it's harder to prove the negative. I remember many years ago this wasn't the case, and I had to thread the connect phase, but the ChangeLog suggests that things have changed considerably. Connect has been asynch for years, though an option to configure the connect timeout is a more recent addition. The only significant thing left that I can think of that's still only synchronous is ldap_sasl_interactive_bind_s(), and I have some plans to fix that. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/
On Mon, Nov 8, 2010 at 5:57 PM, Howard Chu hyc@symas.com wrote:
Shankar Anand R wrote:
Hi,
Is there any workaround way by which we will be able to do a DIGEST-MD5 - SASL LDAP bind asynchronously?
Howard: Is there a plan to have an asynchronous ldap_sasl_interactive_bind in the near future? Any time lines for that?
No future plan. It's in CVS as of October 13, so it's already in the past.
Great! Thanks for the information.
I understand that the openldap project does not follow strict release dates. But I see that there is an average of 3 months between 2.4.x and 2.4.x+1. Can you help me by giving an approximate date when 2.4.24 will be released (with this fix)?
Thanks,
Shankar
On Mon, Oct 11, 2010 at 3:06 PM, Howard Chu <hyc@symas.com mailto:hyc@symas.com> wrote:
William Ahern wrote:
Excepting DNS, is the latest release of OpenLDAP fully asynchronous-capable, even with TLS? Perusing the source code I can't find any obviousplaces other than DNS where things might block, but it's harder to prove the negative.
I remember many years ago this wasn't the case, and I had to threadthe connect phase, but the ChangeLog suggests that things have changed considerably.
Connect has been asynch for years, though an option to configure the connect timeout is a more recent addition.
The only significant thing left that I can think of that's still only synchronous is ldap_sasl_interactive_bind_s(), and I have some plans to fix that. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/
-- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/
Shankar Anand R wrote:
On Mon, Nov 8, 2010 at 5:57 PM, Howard Chu <hyc@symas.com mailto:hyc@symas.com> wrote:
Shankar Anand R wrote: Hi, Is there any workaround way by which we will be able to do a DIGEST-MD5 - SASL LDAP bind asynchronously? Howard: Is there a plan to have an asynchronous ldap_sasl_interactive_bind in the near future? Any time lines for that? No future plan. It's in CVS as of October 13, so it's already in the past.Great! Thanks for the information. I understand that the openldap project does not follow strict release dates. But I see that there is an average of 3 months between 2.4.x and 2.4.x+1. Can you help me by giving an approximate date when 2.4.24 will be released (with this fix)?
No idea. You can help by actually using/testing the code and giving feedback on how it worked out for you. If it still has problems, then it cannot be released sooner. If no one is actually going to use it, then it will not be released.
openldap-technical@openldap.org
-
Howard Chu -
Shankar Anand R -
William Ahern