[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Asynchronicity
- To: openldap-technical@openldap.org
- Subject: Asynchronicity
- From: William Ahern <william@25thandClement.com>
- Date: Sat, 9 Oct 2010 16:31:40 -0700
- Content-disposition: inline
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=25thandClement.com; s=jan2009; t=1286667100; bh=IaPkB3MdxpwH7ooBWFlR65UxD12JKSvgVCtpGe4aFqM=; h=Date:From:To:Subject:Message-ID:Mime-Version:Content-Type; b=qDgq88hADH8O8XDmfs+ikeLAlxtNVV3AkwgOQSDQFPyILhquiYWCfDcPDEuL5PgTd r1I7nLAbzI++rAo3WN1M9ocrtL0R6GoOpjGo7dIlYNpMnK+v0yLYyWQ85LTv1xII99 RhuEJ8n5k3N1/llZ3jBQDODXWBb2qkqJ0vyRFcfw=
- User-agent: Mutt/1.4.2.3i
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.