Capability of specifying timeout per service client instance

[svejdo1]

Currently the max connection timeout is static-only - ServiceClient.MaxConnectionTimeout; this is inconvenient for situation like having a service than handles async workload (where long waiting is tolerable, desired even sometimes for some kind of metadata publishing) and sync workload (where waiting is not tolerable - we need to fail fast as user won't wait behind browser for our service to communicate with slow dataverse).

Would it be possible to specify the timeout per service client instance instead ?

[MattB-msft]

This is something we can look at for future enhancement, and might be a good candidate for the "with" pattern we are considering implementing for several things.

[8ggmaker]

@MattB-msft is the MaxConnectionTimeout the same as the execution timeout, I see the default value of MaxConnectionTimeout is 2 minute, but we see some execution timeout of 4 minute