Hi Linvi,
Just looking at the src for HttpClientWebHelper & TwitterTimeoutException, it looks like you've changed the way timeouts get set between 0.9.8 and 0.9.9 so that each query can have its own timeout (as could be set using the snippet you supplied me with), but the value printed in the Exception is still taken from ITweetinviSettingsAccessor.
The value on ITweetinviSettingsAccessor won't reflect the value for that query, and also wont reflect the default value used by HttpClientWebHelper (gets set in the snippet you've posted in your last message).
So it looks to me like the timeout is actually correct, but the value printed in the exception is wrong.
Also, I'd have previously set a request timeout with
Cheers,
Josh
Just looking at the src for HttpClientWebHelper & TwitterTimeoutException, it looks like you've changed the way timeouts get set between 0.9.8 and 0.9.9 so that each query can have its own timeout (as could be set using the snippet you supplied me with), but the value printed in the Exception is still taken from ITweetinviSettingsAccessor.
The value on ITweetinviSettingsAccessor won't reflect the value for that query, and also wont reflect the default value used by HttpClientWebHelper (gets set in the snippet you've posted in your last message).
So it looks to me like the timeout is actually correct, but the value printed in the exception is wrong.
Also, I'd have previously set a request timeout with
TweetinviConfig.APPLICATION_WEB_REQUEST_TIMEOUT = 0;
but the new implementation just uses a hardcoded value of 10. Shouldn't it fall back to APPLICATION_WEB_REQUEST_TIMEOUT or is this an intended change?Cheers,
Josh