direct YAML support in the API available today), the Content-Type and Accept
headers are now properly handled as per the HTTP spec.  As a consequence, if
you had a client that was sending an invalid Content-Type or Accept header to
the API, in 1.2 you will either receive a 415 or 406 error.
The only client
this is known to affect is curl when you use -d with JSON but don't set a
content type, helpfully sends "application/x-www-urlencoded", which is not

	setDriveCounts := make([]int, len(z.serverPools))
	for i := range z.serverPools {
		setDriveCounts[i] = z.serverPools[i].SetDriveCount()
	}
	return setDriveCounts
}

type serverPoolsAvailableSpace []poolAvailableSpace

type poolAvailableSpace struct {
	Index      int
	Available  uint64 // in bytes
	MaxUsedPct int    // Used disk percentage of most filled disk, rounded down.
}

    }
  }

  private fun buildRequest(
    hostname: String,
    type: Int,
  ): Request =
    Request
      .Builder()
      .header("Accept", DNS_MESSAGE.toString())
      .apply {
        val query = DnsRecordCodec.encodeQuery(hostname, type)

        val dnsUrl: HttpUrl = ******@****.***
        if (post) {
          url(dnsUrl)

                logError("Error updating file", e);
            }
        }

        return true;
    }

    /**
     * Gets the fully qualified class name for a type element, including handling inner classes.
     *
     * @param typeElement the type element to get the class name for
     * @return the fully qualified class name
     */
    private String getFullClassName(TypeElement typeElement) {

    Artifact createArtifact(String groupId, String artifactId, String version, String scope, String type);

    Artifact createProjectArtifact(String groupId, String artifactId, String version);

    Artifact createArtifactWithClassifier(
            String groupId, String artifactId, String version, String type, String classifier);

    Artifact createPluginArtifact(Plugin plugin);

    Note over Client: Keeps consuming...
```

它甚至可以是無限串流，你可以一直持續傳送資料。

## JSON Lines { #json-lines }

在這些情況下，常見做法是傳送「**JSON Lines**」，這是一種每一行各包含一個 JSON 物件的格式。

回應的 content type 會是 `application/jsonl`（而不是 `application/json`），而本體內容會像這樣：

```json
{"name": "Plumbus", "description": "A multi-purpose household device."}
{"name": "Portal Gun", "description": "A portal opening device."}

 * @param <K0> An upper bound on the key type of the generated multimap.
 * @param <V0> An upper bound on the value type of the generated multimap.
 * @since 16.0
 */
@GwtCompatible
public abstract class MultimapBuilder<K0 extends @Nullable Object, V0 extends @Nullable Object> {
  /*
   * Leaving K and V as upper bounds rather than the actual key and value types allows type

 * @param <K0> An upper bound on the key type of the generated multimap.
 * @param <V0> An upper bound on the value type of the generated multimap.
 * @since 16.0
 */
@GwtCompatible
public abstract class MultimapBuilder<K0 extends @Nullable Object, V0 extends @Nullable Object> {
  /*
   * Leaving K and V as upper bounds rather than the actual key and value types allows type

        for (int i = 8; i < 31; i += 2) {
            assertEquals('C', dst[i + 1]);
            assertEquals('A', dst[i + 2]);
        }

        // Check type encoding at position 31-32
        assertEquals('C', dst[31]); // (0x20 >> 4) + 0x41 = 'C'
        assertEquals('A', dst[32]); // (0x20 & 0x0F) + 0x41 = 'A'

        // Verify length
        assertTrue(length > 33);

    val responseCode = userResponse.code

    val method = userResponse.request.method
    when (responseCode) {
      HTTP_PROXY_AUTH -> {
        val selectedProxy = route!!.proxy
        if (selectedProxy.type() != Proxy.Type.HTTP) {
          throw ProtocolException("Received HTTP_PROXY_AUTH (407) code while not using proxy")
        }
        return chain.proxyAuthenticator.authenticate(route, userResponse)
      }