Uploaded image for project: 'HttpComponents HttpClient'
  1. HttpComponents HttpClient
  2. HTTPCLIENT-2262

Clarify infinite timeout vs disabled timeout

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Information Provided
    • 5.2.1
    • None
    • HttpClient (classic)
    • None

    Description

      I have a question regarding the expected behavior when setting a timeout to 0.

      In HttpClient, If I read for example the Javadoc of the connectionRequestTimeout, it tells me that a timeout of 0 is infinite.

      In HttpCore, If I read the Javadoc of Timeout#DISABLED, it tells me that the timeout is simply disabled when set to 0 but what disabled means precisely?

      If I keep digging in HttpCore, I see several classes like StrictConnPool that leverage Future and Lock for which a timeout set to 0, means that we expect an immediate result either with a success or a TimeoutException, so I assume that it is what "disabled timeout" means but if so it would be in conflict with an infinite timeout as I personally don't expect to get a TimeoutException in case of an infinite timeout but maybe I'm wrong and it just needs to be clarified?

      Attachments

        Activity

          People

            Unassigned Unassigned
            nfilotto Nicolas Filotto
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: