lethinker commented on PR #694:
URL: 
https://github.com/apache/httpcomponents-client/pull/694#issuecomment-3166241851

   > > It seems that the effected ResponseTimeout is being rounded up to the 
nearest second, and milliseconds are not taking effect.
   > 
   > @lethinker Socket timeout granularity of async connections is one second 
(can be reduced at the cost of the i/o reactor running in a tighter loop and 
waking up more often, and causing higher CPU utilization). Socket timeout 
granularity of blocking connections is _approximately_ 10 ms.
   > 
   > Timeouts in ms make no sense.
   
   Thank you for your help.
   Is there any plan to support 10ms granularity timeout control in async 
connections in the fulture?
   I just have the business scenario  to use  a timeout interval of 100ms, If 
the response time exceeds 100ms, I want to discard the message.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org

Reply via email to