Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 8 of 8 for Mayer (0.2 sec)

  1. okhttp/src/main/kotlin/okhttp3/Callback.kt

       * response body is [closed][ResponseBody]. The recipient of the callback may consume the response
       * body on another thread.
       *
       * Note that transport-layer success (receiving a HTTP response code, headers and body) does not
       * necessarily indicate application-layer success: `response` may still indicate an unhappy HTTP
       * response code like 404 or 500.
       */
      @Throws(IOException::class)
      fun onResponse(
        call: Call,
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Mon Jan 08 01:13:22 GMT 2024
    - 1.6K bytes
    - Viewed (0)
  2. docs/features/events.md

    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.
    
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Sun Feb 06 02:19:09 GMT 2022
    - 7.7K bytes
    - Viewed (0)
  3. docs/contribute/concurrency.md

    ### Threads
    
    #### Application's calling thread
    
    The application-layer must block on writing I/O. We can't return from a write until we've pushed its bytes onto the socket. Otherwise, if the write fails we are unable to deliver its IOException to the application. We would have told the application layer that the write succeeded, but it didn't!
    
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Sun Feb 06 16:35:36 GMT 2022
    - 7K bytes
    - Viewed (0)
  4. okhttp/src/main/kotlin/okhttp3/Call.kt

       * leaking resources callers must [close the response body][ResponseBody] or the response.
       *
       * Note that transport-layer success (receiving a HTTP response code, headers and body) does not
       * necessarily indicate application-layer success: `response` may still indicate an unhappy HTTP
       * response code like 404 or 500.
       *
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Wed Dec 20 23:27:07 GMT 2023
    - 3.6K bytes
    - Viewed (0)
  5. okhttp-tls/Module.md

    # Module okhttp-tls
    
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Tue Apr 02 11:27:49 GMT 2019
    - 68 bytes
    - Viewed (0)
  6. docs/works_with_okhttp.md

     * [Communicator](https://github.com/Taig/Communicator): An OkHttp wrapper for Scala built with Android in mind.
     * [Cronet Transport for OkHttp](https://github.com/google/cronet-transport-for-okhttp): A HTTP3 ready transport layer for OkHttp on Android, based on Chromium network stack.
     * [CWAC-NetSecurity](https://github.com/commonsguy/cwac-netsecurity): Simplifying Secure Internet Access.
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Wed Jun 08 18:15:23 GMT 2022
    - 3.8K bytes
    - Viewed (0)
  7. okhttp/src/main/kotlin/okhttp3/Dispatcher.kt

       * callback has returned. Synchronous calls become idle once [execute()][Call.execute] returns.
       * This means that if you are doing synchronous calls the network layer will not truly be idle
       * until every returned [Response] has been closed.
       */
      var idleCallback: Runnable? = null
        get() = this.withLock { field }
        set(value) {
          this.withLock { field = value }
        }
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Sat Apr 20 17:03:43 GMT 2024
    - 9K bytes
    - Viewed (0)
  8. okhttp/src/main/kotlin/okhttp3/Connection.kt

     * to a remote host. Newer TLS options are quite useful:
     *
     *  * Server Name Indication (SNI) enables one IP address to negotiate secure connections for
     *    multiple domain names.
     *
     *  * Application Layer Protocol Negotiation (ALPN) enables the HTTPS port (443) to be used to
     *    negotiate HTTP/2.
     *
     * Unfortunately, older HTTPS servers refuse to connect when such options are presented. Rather than
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Wed Dec 20 23:27:07 GMT 2023
    - 4.3K bytes
    - Viewed (0)
Back to top