You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We had wanted to allow setting of these parameters in the original design of the client but it looks like we haven't implemented it. Purely an oversight on our end. I apologize for that.
I see two options:
We expose methods to set the individual settings, like you suggested above
We allow access to the underlying HttpClient which can be setup how you wish
It looks like we have a public setter for the HttpClient, but the getter is private. I believe we could open up the getter. Then you would be able to mutate it and set it.
I think hiding the HTTP client would be a better design approach. Right
now, setting the individual timeouts is all I need. But this might change
in the future...
I am not sure.
Activity
myagley commentedon Jun 25, 2014
Hi Florian,
We had wanted to allow setting of these parameters in the original design of the client but it looks like we haven't implemented it. Purely an oversight on our end. I apologize for that.
I see two options:
It looks like we have a public setter for the HttpClient, but the getter is private. I believe we could open up the getter. Then you would be able to mutate it and set it.
Which option do you prefer?
Mike
jack-kerouac commentedon Jun 25, 2014
I think hiding the HTTP client would be a better design approach. Right
now, setting the individual timeouts is all I need. But this might change
in the future...
I am not sure.