*
 * This nesting is typical but not strict. For example, when calls use "Expect: continue" the
 * request body start and end events occur within the response header events. Similarly,
 * [duplex calls][RequestBody.isDuplex] interleave the request and response bodies.
 *
 * Since connections may be reused, the proxy selection, DNS, and connect events may not be present

    simultaneously. This can be used to implement interactive conversations within a single HTTP
    call.

    Create duplex calls by overriding the new `RequestBody.isDuplex()` method to return true.
    This simple option dramatically changes the behavior of the request body and of the entire
    call.

    The `RequestBody.writeTo()` method may now retain a reference to the provided sink and

          return null
        }

        override fun writeTo(sink: BufferedSink) {
          sink.writeUtf8("Hello request!")
          sink.close()
        }

        override fun isDuplex(): Boolean {
          return true
        }
      }
    val request =
      request()
        .post(asyncRequestBody)
        .build()
    val response = client.newCall(request).execute()

    var requestBody: RequestBody =
      object : RequestBody() {
        override fun contentType(): MediaType? = TODO()

        override fun contentLength(): Long = TODO()

        override fun isDuplex(): Boolean = TODO()

        override fun isOneShot(): Boolean = TODO()

        override fun writeTo(sink: BufferedSink) = TODO()
      }
    requestBody = "".toRequestBody(null)

	public static final fun create ([BLokhttp3/MediaType;II)Lokhttp3/RequestBody;
	public static final fun gzip (Lokhttp3/RequestBody;)Lokhttp3/RequestBody;
	public fun isDuplex ()Z
	public fun isOneShot ()Z
	public abstract fun writeTo (Lokio/BufferedSink;)V
}

public final class okhttp3/RequestBody$Companion {