* task should not be executed again. Otherwise it returns a delay until the next execution.
 *
 * A task has at most one next execution. If the same task instance is scheduled multiple times, the
 * earliest one wins. This applies to both executions scheduled with [TaskRunner.Queue.schedule] and
 * those implied by the returned execution delay.
 *
 * Cancellation
 * ------------
 *

 *  limitations under the License.
 */
package okhttp3

import java.net.Socket

/**
 * The sockets and streams of an HTTP, HTTPS, or HTTPS+HTTP/2 connection. May be used for multiple
 * HTTP request/response exchanges. Connections may be direct to the origin server or via a proxy.
 *
 * Typically instances of this class are created, connected and exercised automatically by the HTTP

   * called and that value is both inserted and returned.
   *
   * If multiple calls to this function are made concurrently with the same [type], multiple values
   * may be computed. But only one value will be inserted, and that inserted value will be returned
   * to all callers.
   *
   * If computing multiple values is problematic, use an appropriate concurrency mechanism in your

        doNothing().when(smbTree).close();

        smbTree.close();

        verify(smbTree).close();
    }

    /**
     * Test for close() method called multiple times.
     * Verifies that close can be called multiple times safely.
     */
    @Test
    void testClose_multipleTimes() {
        doNothing().when(smbTree).close();

        smbTree.close();
        smbTree.close();

    }

    @Nested
    @DisplayName("Performance and concurrency")
    class PerformanceTests {

        @Test
        @DisplayName("Should handle multiple lookups efficiently")
        void testMultipleLookups() throws IOException {
            // Test that multiple lookups work correctly
            for (int i = 0; i < 100; i++) {
                assertEquals("application/pdf", mimeMap.getMimeType("pdf"));

 * quantiles. All algorithms modify the dataset they are given (the cost of a copy to avoid this
 * will be constant across algorithms).
 *
 * @author Pete Gillin
 * @since 20.0
 */
@NullUnmarked
enum QuantilesAlgorithm {

  /**
   * Sorts the dataset, and picks values from it. When computing multiple quantiles, we sort once
   * and pick multiple values.
   */

	<fieldset class="mb-3">
		<legend><la:message key="labels.index_lang" /></legend>
		<label for="langSearchOption"><la:message key="labels.index_lang" /></label>
		<la:select property="lang" styleId="langSearchOption" multiple="true"
			styleClass="form-control">
			<c:forEach var="item" items="${langItems}">
				<la:option value="${f:u(item.value)}">${f:h(item.label)}</la:option>
			</c:forEach>
		</la:select>
	</fieldset>

	<fieldset class="mb-3">
		<legend><la:message key="labels.index_lang" /></legend>
		<label for="langSearchOption"><la:message key="labels.index_lang" /></label>
		<la:select property="lang" styleId="langSearchOption" multiple="true"
			styleClass="form-control">
			<c:forEach var="item" items="${langItems}">
				<la:option value="${f:u(item.value)}">${f:h(item.label)}</la:option>
			</c:forEach>
		</la:select>
	</fieldset>

There may be many routes for a single address. For example, a webserver that is hosted in multiple datacenters may yield multiple IP addresses in its DNS response.

In limited situations OkHttp will retry a route if connecting fails:

A single HTTP call may require follow-up requests to be made to handle authentication challenges, redirects, and HTTP-layer timeouts. In such cases multiple connections, requests, and responses may be attempted. Follow-ups are another reason a single call may trigger multiple events of the same type.