* @param len the number of bytes to write
     * @param andx the next command in the AndX chain, or null
     */
    public SmbComWriteAndX(final Configuration config, final int fid, final long offset, final int remaining, final byte[] b, final int off,
            final int len, final ServerMessageBlock andx) {
        super(config, SMB_COM_WRITE_ANDX, andx);
        this.fid = fid;
        this.offset = offset;

    private byte[] blob = null;

    /**
     * Constructs a session setup AndX response.
     *
     * @param config the configuration to use
     * @param andx the next command in the AndX chain, or null
     */
    public SmbComSessionSetupAndXResponse(final Configuration config, final ServerMessageBlock andx) {
        super(config, andx);
    }

    /**
     * Returns the native LAN Manager string reported by the server.

{* ../../docs_src/dataclasses/tutorial001.py hl[1,7:12,19:20] *}

Isso ainda é suportado graças ao **Pydantic**, pois ele tem <a href="https://docs.pydantic.dev/latest/concepts/dataclasses/#use-of-stdlib-dataclasses-with-basemodel" class="external-link" target="_blank">suporte interno para `dataclasses`</a>.

        SMBUtil.writeInt2(83, buffer, 36); // andxOffset (33 + 50)
        SMBUtil.writeInt2(20, buffer, 42); // byteCount

        // Setup andx command data at offset 83 (absolute position from buffer start)
        buffer[83] = 2; // andx wordCount
        SMBUtil.writeInt2(10, buffer, 88); // andx byteCount

        int length = testBlock.decode(buffer, 0);

        assertTrue(length > 0);

    /**
     * Constructs an Open AndX request.
     *
     * @param config the configuration
     * @param fileName the name of the file to open
     * @param access the desired access mode
     * @param shareAccess the share access mode
     * @param flags the open flags
     * @param fileAttributes the file attributes
     * @param andx the next command in the chain
     */

    /**
     * Constructs a tree connect AndX request to establish a connection to a shared resource.
     *
     * @param ctx the CIFS context containing configuration
     * @param server the server data containing security information
     * @param path the UNC path to the shared resource
     * @param service the service type (e.g., "A:" for disk share, "LPT1:" for printer)
     * @param andx the next command in the AndX chain, or null
     */

    private int capabilities;

    /**
     * Constructs a session setup AndX request.
     *
     * @param tc the CIFS context containing configuration and credentials
     * @param negotiated the negotiation response containing server capabilities
     * @param andx the next command in the AndX chain, or null
     * @param cred the authentication credentials to use for the session

/**
 * SMB1 Read AndX Response message.
 *
 * This response contains the data that was read from the file
 * along with information about the read operation.
 */
public class SmbComReadAndXResponse extends AndXServerMessageBlock {

    private byte[] data;
    private int offset, dataCompactionMode, dataLength, dataOffset;

    /**
     * Constructs a Read AndX response.
     *

/// tip | Dica

Mas ainda é recomendado usar as ideias acima, usando várias classes, em vez desses parâmetros.

Isso ocorre porque o Schema JSON gerado no OpenAPI do seu aplicativo (e a documentação) ainda será o único para o modelo completo, mesmo que você use `response_model_include` ou `response_model_exclude` para omitir alguns atributos.

## Caso de uso

Por exemplo, imagine que você deseja retornar um código de status HTTP de "OK" `200` por padrão.

Mas se o dado não existir, você quer criá-lo e retornar um código de status HTTP de "CREATED" `201`.

Mas você ainda quer ser capaz de filtrar e converter o dado que você retornará com um `response_model`.

Para estes casos, você pode utilizar um parâmetro `Response`.

## Use um parâmetro `Response`