Skip to content
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

Separate timeout for connect() and call() #20

Open
wosiu opened this issue Sep 9, 2018 · 0 comments
Open

Separate timeout for connect() and call() #20

wosiu opened this issue Sep 9, 2018 · 0 comments

Comments

@wosiu
Copy link

wosiu commented Sep 9, 2018

My use-case:
If I connect to server, I want to know that there is something wrong immediately.
However when I call my client, I want to wait longer, as my calculation in RPC server logic takes a while.
The best would be to be able to provide timeout kwarg to call() method, so that a developer can specify separate timeouts for each call.
Question is, how timeout parameter in call method should be set as a default. 2 ideas:

  1. whatever, like 10 sec
  2. None. In that case timeout which was used for creating Client is used for call as it is done right now - backward compatibility provided.

I may try to develop something and PR, but let me know first what do you think plz.

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

No branches or pull requests

1 participant