Message137916
| Author |
pitrou |
| Recipients |
dsiroky, pitrou |
| Date |
2011年06月08日.16:00:38 |
| SpamBayes Score |
2.9245714e-06 |
| Marked as misclassified |
No |
| Message-id |
<1307548834.12682.1.camel@localhost.localdomain> |
| In-reply-to |
<1307525075.49.0.994783661382.issue12197@psf.upfronthosting.co.za> |
| Content |
> Sorry, I attached wrong example version. It uses repeated
> sslsock.write() of the same buffer after catching
> SSL_ERROR_WANT_WRITE. It delivers the full block but this is a
> blocking operation.
In "normal" non-blocking code you would use select() (or an equivalent)
until the socket is ready for writing, and then send() some chunk of
data on it. Can't you use that approach? |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年06月08日 16:00:38 | pitrou | set | recipients:
+ pitrou, dsiroky |
| 2011年06月08日 16:00:38 | pitrou | link | issue12197 messages |
| 2011年06月08日 16:00:38 | pitrou | create |
|