Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for Meyers (0.2 sec)

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

    import okhttp3.internal.platform.Platform
    import okhttp3.internal.threadName
    import okio.AsyncTimeout
    import okio.Timeout
    
    /**
     * Bridge between OkHttp's application and network layers. This class exposes high-level application
     * layer primitives: connections, requests, responses, and streams.
     *
     * This class supports [asynchronous canceling][cancel]. This is intended to have the smallest
    Plain Text
    - Registered: Fri Apr 26 11:42:10 GMT 2024
    - Last Modified: Sat Apr 20 17:03:43 GMT 2024
    - 17.9K bytes
    - Viewed (2)
  2. okhttp/src/main/kotlin/okhttp3/internal/http2/Http2Stream.kt

      /**
       * The reason why this stream was closed, or null if it closed normally or has not yet been
       * closed.
       *
       * If there are multiple reasons to abnormally close this stream (such as both peers closing it
       * near-simultaneously) then this is the first reason known to this peer.
       */
      internal var errorCode: ErrorCode? = null
        get() = this.withLock { field }
    
    Plain Text
    - Registered: Fri Apr 26 11:42:10 GMT 2024
    - Last Modified: Sat Apr 20 17:03:43 GMT 2024
    - 23.2K bytes
    - Viewed (1)
  3. okhttp-tls/src/main/kotlin/okhttp3/tls/HeldCertificate.kt

     * called certificate authorities (CAs).
     *
     * Browsers and other HTTP clients need a set of trusted root certificates to authenticate their
     * peers. Sets of root certificates are managed by either the HTTP client (like Firefox), or the
     * host platform (like Android). In July 2018 Android had 134 trusted root certificates for its HTTP
     * clients to trust.
     *
    Plain Text
    - Registered: Fri Apr 26 11:42:10 GMT 2024
    - Last Modified: Mon Jan 08 01:13:22 GMT 2024
    - 21.6K bytes
    - Viewed (1)
  4. okhttp/src/main/kotlin/okhttp3/internal/http2/Http2Connection.kt

         * Apply inbound settings and send an acknowledgement to the peer that provided them.
         *
         * We need to apply the settings and ack them atomically. This is because some HTTP/2
         * implementations (nghttp2) forbid peers from taking advantage of settings before they have
         * acknowledged! In particular, we shouldn't send frames that assume a new `initialWindowSize`
         * until we send the frame that acknowledges this new size.
         *
    Plain Text
    - Registered: Fri Apr 26 11:42:10 GMT 2024
    - Last Modified: Sat Apr 20 17:03:43 GMT 2024
    - 32.6K bytes
    - Viewed (0)
Back to top