New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose wait_readable
and wait_writable
in SSLSocket
#408
Comments
Agreed, that would be a nice addition. Other methods from io/wait (#nread - can simply return 0, #ready?, #wait, #wait_priority) can also be implemented in a similar way. |
petergoldstein
added a commit
to petergoldstein/dalli
that referenced
this issue
Oct 15, 2021
petergoldstein
added a commit
to petergoldstein/dalli
that referenced
this issue
Oct 18, 2021
petergoldstein
added a commit
to petergoldstein/dalli
that referenced
this issue
Oct 19, 2021
petergoldstein
added a commit
to petergoldstein/dalli
that referenced
this issue
Oct 20, 2021
petergoldstein
added a commit
to petergoldstein/dalli
that referenced
this issue
Oct 20, 2021
petergoldstein
added a commit
to petergoldstein/dalli
that referenced
this issue
Oct 21, 2021
petergoldstein
added a commit
to petergoldstein/dalli
that referenced
this issue
Oct 22, 2021
petergoldstein
added a commit
to petergoldstein/dalli
that referenced
this issue
Oct 22, 2021
petergoldstein
added a commit
to petergoldstein/dalli
that referenced
this issue
Oct 25, 2021
petergoldstein
added a commit
to petergoldstein/dalli
that referenced
this issue
Oct 25, 2021
petergoldstein
added a commit
to petergoldstein/dalli
that referenced
this issue
Oct 25, 2021
petergoldstein
added a commit
to petergoldstein/dalli
that referenced
this issue
Oct 26, 2021
petergoldstein
added a commit
to petergoldstein/dalli
that referenced
this issue
Oct 27, 2021
petergoldstein
added a commit
to petergoldstein/dalli
that referenced
this issue
Oct 27, 2021
Has this still not happened yet? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems like we don't expose this.
It was a problem for this PR: redis/redis-rb#960
User should be able to expect to write:
But it doesn't seem to be working for
SSLSocket
.It should be relatively trivial to implement, something like this:
Any thoughts?
The text was updated successfully, but these errors were encountered: