M2Crypto: select() behaves weird on SSL sockets
Irmen de Jong
irmen at NOSPAMREMOVETHISxs4all.nl
Fri Jun 28 13:33:44 EDT 2002
Steve Holden wrote:
> asyncore/asynchat really repay the effort of study, so I would advise you to
> take a fresh look when you get time.
I will. Am I correct to conclude that the benefits of using asyncore as a
basis for Pyro are:
1. uses a well-tested stable I/O module (though the current implementation
in Pyro isn't bad at all)
2. able to process multiple requests without using threads, because
the I/O is multiplexed
3. able to handle very many concurrent connections (no thread overhead
per connection -- but is a thread really that heavy?)
> To assist you, I plan to add documentation for asynchat for 2.3.
That's nice because I was looking for that one just yet :)
But glancing at the code of asynchat makes me think that this
one isn't suited for Pyro because Pyro is no line-based command-response
protocol.
> when-sourceforge-stops-playing-silly-buggers-ly y'rs - steve
What's wrong with SF?
Cya
Irmen de Jong
More information about the Python-list
mailing list