Author dsiroky
Recipients dsiroky, pitrou
Date 2011-06-08.09:24:31
SpamBayes Score 3.24865e-09
Marked as misclassified No
Message-id <1307525075.49.0.994783661382.issue12197@psf.upfronthosting.co.za>
In-reply-to
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.

I'm troubled with non-blocking writes. But as I dig deeper into the problem it looks like an inconsistency in OpenSSL (Linux vs. MSW). In Linux sslsock.write() always (as far as I can tell) sends some or all of the data and returns the amount. Like the plain socket.send(). In Windows it raises an exception if the data is larger then some uncertain size (mostly 16kB).

I'm working on snakeMQ asynchronous messaging library where the "packeter" layer relies on the sock.send() returning actual amount of sent bytes. This is not working in Windows if the link uses SSL.

Tested on WinXP, py2.6, py3.2.
History
Date User Action Args
2011-06-08 09:24:35dsirokysetrecipients: + dsiroky, pitrou
2011-06-08 09:24:35dsirokysetmessageid: <1307525075.49.0.994783661382.issue12197@psf.upfronthosting.co.za>
2011-06-08 09:24:32dsirokylinkissue12197 messages
2011-06-08 09:24:31dsirokycreate