Those worker processes would be the ones running your application, they would perform the main computations to receive a **request** and return a **response**, and they would load anything you put in variables in RAM.

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

            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">

		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 */

</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}`.

        @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);

</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}`.

The default is tlsmaxrsasize=8192, limiting RSA to 8192-bit keys. To avoid
denial of service attacks, this setting and default was backported to Go
1.19.13, Go 1.20.8, and Go 1.21.1.

Go 1.22 made it an error for a request or response read by a net/http
client or server to have an empty Content-Length header.
This behavior is controlled by the `httplaxcontentlength` setting.

Go 1.22 changed the behavior of ServeMux to accept extended

  <mime-type type="application/mbms-msk+xml"/>
  <mime-type type="application/mbms-msk-response+xml"/>
  <mime-type type="application/mbms-protection-description+xml"/>
  <mime-type type="application/mbms-reception-report+xml"/>
  <mime-type type="application/mbms-register+xml"/>
  <mime-type type="application/mbms-register-response+xml"/>
  <mime-type type="application/mbms-user-service-description+xml"/>