Message117358
| Author |
giampaolo.rodola |
| Recipients |
BreamoreBoy, dmalcolm, giampaolo.rodola, josiahcarlson, matejcik, pitrou, santoso.wijaya |
| Date |
2010年09月25日.11:43:39 |
| SpamBayes Score |
0.0001116101 |
| Marked as misclassified |
No |
| Message-id |
<1285415021.97.0.618894500609.issue6706@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> I'm not convinced hiding operating system bugs is a good idea.
Do you propose to let the error raise then?
The point of frameworks such as asyncore and twisted is to hide all system-specific errors as much as possible and provide a portable interface across all platforms.
AFAICT, the whole point of this issue is that there should be only one way for an asyncore-based server to accept an incoming connection, possibly avoiding the user to deal with low-level details such as catching EWOULDBLOCK/ECONNABORTED/... in his application, and looking for accept() returning None is one possibility.
As I said, in a better designed framework the user shouldn't be supposed to call accept() at all, but that's how asyncore is designed. |
|