Skip to content

Conversation

@evanphx
Copy link
Member

@evanphx evanphx commented Apr 14, 2017

This implementation of write_nonblock is not technically correct because it can block, but at least it gets past #1189 for the time being.

The situation is that implementing it properly means having to be able to rewind the state of OpenSSL, which is hardly trivial.

Copy link
Contributor

@schneems schneems left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One minor typo. Other than that 👍

# is that it means we'd have to have the ability to rewind
# an engine because after we write+extract, the socket
# write_nonblock call might raise an exception and later
# code would pass the same data in, but the engine would thing
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thing => think

@nateberkopec nateberkopec merged commit 7cd363f into master May 1, 2017
@nateberkopec nateberkopec deleted the f-minissl-fix branch November 17, 2017 19:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants