[issue3899] test_ssl.py doesn't properly test ssl integration with asyncore

Antoine Pitrou added the comment: This has been integrated long ago. -- nosy: +pitrou resolution: -> out of date status: open -> closed ___ Python tracker ___ __

[issue3899] test_ssl.py doesn't properly test ssl integration with asyncore

Bill Janssen <[EMAIL PROTECTED]> added the comment: Sure, no argument. I was just making clear what was going on. Bill On Thu, Sep 18, 2008 at 7:33 PM, Josiah Carlson <[EMAIL PROTECTED]>wrote: > > Josiah Carlson <[EMAIL PROTECTED]> added the comment: > > Being able to test the async features

[issue3899] test_ssl.py doesn't properly test ssl integration with asyncore

Josiah Carlson <[EMAIL PROTECTED]> added the comment: Being able to test the async features of both sides of the SSL connection is a good thing. Also, the subclass provides a useful example for users who want to use asyncore and ssl servers without blocking on an incoming connection.

[issue3899] test_ssl.py doesn't properly test ssl integration with asyncore

Bill Janssen <[EMAIL PROTECTED]> added the comment: The server wasn't meant to be non-blocking. The non-blocking test is performed when the client (which is non-blocking) connects to it. ___ Python tracker <[EMAIL PROTECTED]>

[issue3899] test_ssl.py doesn't properly test ssl integration with asyncore

New submission from Giampaolo Rodola' <[EMAIL PROTECTED]>: The AsyncoreEchoServer class in test_ssl.py doesn't actually test a real integration with asyncore since the do_handshake_on_connect flag is set to True and hence temporarily blocks the asyncore polling loop as long as the ssl handshake f