when(tree.isSMB2()).thenReturn(false);
        when(tree.getConfig()).thenReturn(config);
        when(config.getPid()).thenReturn(1234);

        // Stub send to populate the provided response instance via reflection
        Mockito.doAnswer(inv -> {
            Object resp = inv.getArgument(1);
            // Set private fields: status on SmbComTransactionResponse and available on TransPeekNamedPipeResponse

{* ../../docs_src/custom_request_and_route/tutorial003_py310.py hl[26] *}

В этом примере *операции пути*, объявленные в `router`, будут использовать пользовательский класс `TimedRoute` и получат дополнительный HTTP-заголовок `X-Response-Time` в ответе с временем, затраченным на формирование ответа:

        verify(cancelRequest).setSignSeq(10);
        // Sequence should increment by 1 for cancel requests
    }

    @Test
    @DisplayName("Test sign method with null response")
    void testSignWithNullResponse() {
        SMB1SigningDigest digest = new SMB1SigningDigest(testMacSigningKey, false, 10);
        byte[] data = new byte[100];

Está diseñado para tener funciones que reciben dos parámetros, un "request" y un "response". Luego "lees" partes del request y "escribes" partes en el response. Debido a este diseño, no es posible declarar parámetros de request y cuerpos con las anotaciones de tipos estándar de Python como parámetros de función.

 */
package jcifs.internal.smb2.ioctl;

import jcifs.Decodable;
import jcifs.internal.SMBProtocolDecodingException;
import jcifs.internal.util.SMBUtil;

/**
 * SMB2 Validate Negotiate Info response data structure. This structure contains the server's
 * validation of the originally negotiated SMB2 dialect.
 *
 * @author mbechler
 *
 */
public class ValidateNegotiateInfoResponse implements Decodable {

/**
 * SMB1 transaction subcommand for transacting with a named pipe.
 *
 * This class implements the TRANS_TRANSACT_NAMED_PIPE transaction which
 * combines writing data to a pipe and reading the response in a single operation.
 * This is more efficient than separate write and read operations.
 */
public class TransTransactNamedPipe extends SmbComTransaction {

{* ../../docs_src/header_params/tutorial003_an_py310.py hl[9] *}

Si te comunicas con esa *path operation* enviando dos headers HTTP como:

```
X-Token: foo
X-Token: bar
```

El response sería como:

```JSON
{
    "X-Token values": [
        "bar",
        "foo"
    ]
}
```

## Recapitulación { #recap }

 * <p>
 * This class is immutable and thread-safe, suitable for use in concurrent operations.
 *
 * @param <REQ> The type of the request
 * @param <REP> The type of the response, which must extend {@code Result<REQ>}
 * @param request The original request that was processed
 * @param result The result of the request, if successful; may be null if an error occurred

Ein <abbr title="Anfragekörper">**Request**body</abbr> sind Daten, die vom Client zu Ihrer API gesendet werden. Ein <abbr title="Antwortkörper">**Response**body</abbr> sind Daten, die Ihre API zum Client sendet.

Ihre API muss fast immer einen **Response**body senden. Aber Clients müssen nicht unbedingt immer **Requestbodys** senden, manchmal fordern sie nur einen Pfad an, vielleicht mit einigen Query-Parametern, aber senden keinen Body.

type UserRequest struct {
	URL     string      `json:"url"`
	Headers http.Header `json:"headers"`
}

// GetObjectContext provides the necessary details to perform
// download of the object, and return back the processed response
// to the server.
type GetObjectContext struct {
	OutputRoute string `json:"outputRoute"`
	OutputToken string `json:"outputToken"`
	InputS3URL  string `json:"inputS3Url"`
}