Hi Simone,
Thanks for the clarifications.
Regarding retries, that was the point I was making as well. If our application retries, it will be treated no different than other request and will be queued and processed as other requests.
Thanks for clarifying the blocking connect. I have a further clarification in this regard for synchronous requests. Here, for every request, we can provide a timeout that governs the time for request/response conversation to complete.
Now, the request/response processing involves making a connection with the target end point, sending the request and receiving the response from the target end point. While working with other libraries eg. Apache, we make use of 2 properties: connectionTimeout (timeout for establishing connections) and socketTimeout (timeout to read the response). Using the same terminology, how should the request timeout value be configured for synchronous Jetty requests.
Should it be connectionTimeout + socketTimeout or atleast a value that is greater that connectionTimeout so that we sufficienty allocate time for connection creation and reading the response.
Thanks
Neha