Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 9 of 9 for coalesce (0.16 sec)

  1. okhttp/src/main/kotlin/okhttp3/internal/connection/RealConnection.kt

      }
    
      /**
       * Returns true if this connection's route has the same address as any of [candidates]. This
       * requires us to have a DNS address for both hosts, which only happens after route planning. We
       * can't coalesce connections that use a proxy, since proxies don't tell us the origin server's IP
       * address.
       */
      private fun routeMatchesAny(candidates: List<Route>): Boolean {
        return candidates.any {
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Sat Apr 20 17:03:43 GMT 2024
    - 15.4K bytes
    - Viewed (0)
  2. okhttp/src/main/kotlin/okhttp3/internal/http/RetryAndFollowUpInterceptor.kt

              return userResponse.request
            }
    
            return null
          }
    
          HTTP_MISDIRECTED_REQUEST -> {
            // OkHttp can coalesce HTTP/2 connections even if the domain names are different. See
            // RealConnection.isEligible(). If we attempted this and the server returned HTTP 421, then
            // we can retry on a different connection.
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Mon Apr 15 13:24:48 GMT 2024
    - 12.1K bytes
    - Viewed (4)
  3. okhttp/src/main/kotlin/okhttp3/internal/connection/ConnectPlan.kt

        user.updateRouteDatabaseAfterSuccess(route)
    
        val connection = this.connection!!
        user.connectionConnectEnd(connection, route)
    
        // If we raced another call connecting to this host, coalesce the connections. This makes for
        // 3 different lookups in the connection pool!
        val pooled3 = routePlanner.planReusePooledConnection(this, routes)
        if (pooled3 != null) return pooled3.connection
    
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Sat Apr 20 17:03:43 GMT 2024
    - 18.6K bytes
    - Viewed (0)
  4. okhttp/src/test/java/okhttp3/ConnectionCoalescingTest.kt

       * - 2 requests happen concurrently to a host that can be coalesced onto a single connection.
       * - Both request discover no existing connection. They both make a connection.
       * - The first request "wins the race".
       * - The second request discovers it "lost the race" and closes the connection it just opened.
       * - The second request uses the coalesced connection from request1.
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Sat Jan 20 10:30:28 GMT 2024
    - 18.7K bytes
    - Viewed (0)
  5. okhttp/src/main/kotlin/okhttp3/internal/connection/RealConnectionPool.kt

       * unhealthy connections in its search, this will clean them up.
       *
       * If [routes] is non-null these are the resolved routes (ie. IP addresses) for the connection.
       * This is used to coalesce related domains to the same HTTP/2 connection, such as `square.com`
       * and `square.ca`.
       */
      fun callAcquirePooledConnection(
        doExtensiveHealthChecks: Boolean,
        address: Address,
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Sat Apr 20 17:03:43 GMT 2024
    - 16.2K bytes
    - Viewed (0)
  6. docs/changelogs/changelog_4x.md

        Again Later), and 1014 (invalid response from the upstream).
     *  New: Build with Kotlin 1.3.41, BouncyCastle 1.62, and Conscrypt 2.2.1.
     *  Fix: Recover gracefully when a coalesced connection immediately goes unhealthy.
     *  Fix: Defer the `SecurityException` when looking up the default proxy selector.
     *  Fix: Don't use brackets formatting IPv6 host names in MockWebServer.
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Wed Apr 17 13:25:31 GMT 2024
    - 25.2K bytes
    - Viewed (0)
  7. docs/changelogs/changelog_3x.md

        could use new flow control capacity before acknowledging it, causing strict HTTP/2 servers to
        fail the call.
    
     *  Fix: Recover gracefully when a coalesced connection immediately goes unhealthy.
    
    ## Version 3.14.2
    
    _2019-05-19_
    
     *  Fix: Lock in a route when recovering from an HTTP/2 connection error. We had a bug where two
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Sun Feb 06 14:55:54 GMT 2022
    - 50.8K bytes
    - Viewed (0)
  8. okhttp/src/main/kotlin/okhttp3/internal/connection/RealRoutePlanner.kt

            routes = routes,
            requireMultiplexed = planToReplace != null && planToReplace.isReady,
          ) ?: return null
    
        // If we coalesced our connection, remember the replaced connection's route. That way if the
        // coalesced connection later fails we don't waste a valid route.
        if (planToReplace != null) {
          nextRouteToTry = planToReplace.route
          planToReplace.closeQuietly()
        }
    
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Sat Apr 20 17:03:43 GMT 2024
    - 12K bytes
    - Viewed (0)
  9. okhttp/src/main/kotlin/okhttp3/RequestBody.kt

       *  * A authorization challenge (HTTP 401 and 407) that is satisfied by the [Authenticator].
       *  * A retryable server failure (HTTP 503 with a `Retry-After: 0` response header).
       *  * A misdirected request (HTTP 421) on a coalesced connection.
       */
      open fun isOneShot(): Boolean = commonIsOneShot()
    
      companion object {
        /**
         * Returns a new request body that transmits this string. If [contentType] is non-null and lacks
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Thu Jan 25 14:41:37 GMT 2024
    - 9.6K bytes
    - Viewed (0)
Back to top