Chris Lewis wrote:
As a FYI, TLS with async is also an issue for us. I'll be testing your patch on a VERY large spamtrap in the next little while.
Very cool. As I understand the code in IO::Socket::SSL::start_SSL, the patch I provided forces blocking on the socket being upgraded, which could defeat the purpose of the patch if there are slow clients being upgraded.
Maybe this is why there were previous statements on this list explaining that it might not be too simple to upgrade the connection to SSL using async.
I'll continue to dig, and hopefully figure out how to unblock the SSL negotiation.
Thanks, -- Douglas
