@Test
        @DisplayName("Should handle zero sam pointer correctly")
        void testDecodeOutZeroSamPointer() throws NdrException {
            // Given: Message with non-null sam and zero pointer in response
            samr.SamrSamArray samArray = spy(new samr.SamrSamArray());
            samr.SamrEnumerateAliasesInDomain message = new samr.SamrEnumerateAliasesInDomain(mockPolicyHandle, 1, 2, samArray, 3);

            params.put("Requested Time", FessFunctions.formatDate(e.getRequestedAt()));
            params.put("Query Time", toNumberString(e.getQueryTime()));
            params.put("Response Time", toNumberString(e.getResponseTime()));
            params.put("Hit Count", toNumberString(e.getHitCount()));
            params.put("Offset", toNumberString(e.getQueryOffset()));

Esos worker processes serían los que ejecutan tu aplicación, realizarían los cálculos principales para recibir un **request** y devolver un **response**, y cargarían cualquier cosa que pongas en variables en RAM.

<img src="/img/deployment/concepts/process-ram.drawio.svg">

</details>

### Check it { #check-it }

Open your browser at <a href="http://127.0.0.1:8000/items/5?q=somequery" class="external-link" target="_blank">http://127.0.0.1:8000/items/5?q=somequery</a>.

You will see the JSON response as:

```JSON
{"item_id": 5, "q": "somequery"}
```

You already created an API that:

* Receives HTTP requests in the _paths_ `/` and `/items/{item_id}`.

</details>

### Revísalo { #check-it }

Abre tu navegador en <a href="http://127.0.0.1:8000/items/5?q=somequery" class="external-link" target="_blank">http://127.0.0.1:8000/items/5?q=somequery</a>.

Verás el response JSON como:

```JSON
{"item_id": 5, "q": "somequery"}
```

Ya creaste una API que:

* Recibe requests HTTP en los _paths_ `/` y `/items/{item_id}`.

		for _, drive := range drives {
			if drive.State == madmin.DriveStateOk {
				count++
			}
		}
		return count
	}

	// task queued, now wait for the response.
	select {
	case res := <-task.respCh:
		if res.err == nil {
			h.countHealed(healType)
		} else {
			h.countFailed(healType)
		}
		if !h.reportProgress {

    protected int sessionLimit = SmbConstants.DEFAULT_SSN_LIMIT;
    /** Whether to disable Nagle's algorithm for TCP connections */
    protected boolean smbTcpNoDelay = false;
    /** Response timeout in milliseconds for SMB operations */
    protected int smbResponseTimeout = SmbConstants.DEFAULT_RESPONSE_TIMEOUT;
    /** Socket timeout in milliseconds for SMB connections */

          3,
          'B'.code,
          'a'.code,
          'R'.code,
        ),
      ).readHeaders()
    }.also { expected ->
      assertThat(expected.message).isEqualTo(
        "PROTOCOL_ERROR response malformed: mixed case name: Foo",
      )
    }
  }

  @Test
  fun emptyHeaderName() {
    hpackWriter!!.writeByteString("".encodeUtf8())
    assertBytes(0)

</details>

### Check it

Open your browser at <a href="http://127.0.0.1:8000/items/5?q=somequery" class="external-link" target="_blank">http://127.0.0.1:8000/items/5?q=somequery</a>.

You will see the JSON response as:

```JSON
{"item_id": 5, "q": "somequery"}
```

You already created an API that:

* Receives HTTP requests in the _paths_ `/` and `/items/{item_id}`.

This is the case for most of the web applications.

Many, many users, but your server is waiting 🕙 for their not-so-good connection to send their requests.

And then waiting 🕙 again for the responses to come back.

This "waiting" 🕙 is measured in microseconds, but still, summing it all, it's a lot of waiting in the end.

That's why it makes a lot of sense to use asynchronous ⏸🔀⏯ code for web APIs.