Concurrency models (was: Timer)

[Itamar Shtull-Trauring]

Alan Kennedy <alanmk at hotmail.com> wrote in message news:<3F9E74DB.3148DFD1 at hotmail.com>...

> My understanding is that using SSL in non-blocking mode is problematic
> because SSL-level packets can trigger readiness notification on an SSL
> socket when in fact there is no application-level data available.
> 
> Here is a link that discusses the problem
> 
> http://www.openssl.org/support/faq.html#PROG9

Twisted does the right thing and makes sure the user doesn't have to
worry about this. Using SSL is just as easy as using TCP in Twisted.

There are other issues with event loops, like the fact the RSA
handshake is very expensive so you want to run it in another thread.
If Twisted ever has performance issues due to this I'll probably
change the code to do just that, move the handshake stage to a
threadpool.