-
Notifications
You must be signed in to change notification settings - Fork 87
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
How to cancel an idle connection #121
Comments
Hmm, that's a little tricky to do, but I think it may be possible. Specifically, if you are on a Unix system, you should be able to establish the connection yourself first (using |
Thanks, started looking into this, and it almost works, but |
Hmm, why do you need |
When I am using my own stream I can not use `connect` or `connect_insecure`, which call the read_greeting. I do call `login` afterwards, but I thought the greeting reading would be still needed
…On 10. May 2019, 18:27 +0100, Jon Gjengset ***@***.***>, wrote:
Hmm, why do you need read_greeting to be public? Is Client::login not sufficient?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
You should be able to do |
yes that works 👌 |
I need to support the following API
idle
usingwait
idle
and shutting down the connection.Is this possible with the current api and I am missing something, or is there something that needs to be added?
The text was updated successfully, but these errors were encountered: