I am opening this issue to add a few new features that would allow for greater control over the timeouts of both opening connections and individual operations.
As it is right now opening connections inherit the default timeout value of usocket:socket-connect. We could have more flexibility if that value was configurable. Additionally, a global timeout for all commands could be added, as well as the option to make the timeouts signal an error. I noticed some commands already support it as an argument but a default value for the rest would be really useful.
I have done a thorough review of the changes that need to be made in order to support this. They are very few and sensible defaults could be set so as to not affect existing users.
Hello!
I am opening this issue to add a few new features that would allow for greater control over the timeouts of both opening connections and individual operations.
As it is right now opening connections inherit the default timeout value of
usocket:socket-connect
. We could have more flexibility if that value was configurable. Additionally, a global timeout for all commands could be added, as well as the option to make the timeouts signal an error. I noticed some commands already support it as an argument but a default value for the rest would be really useful.I have done a thorough review of the changes that need to be made in order to support this. They are very few and sensible defaults could be set so as to not affect existing users.