import jcifs.internal.smb2.ServerMessageBlock2Response;
import jcifs.internal.util.SMBUtil;

/**
 * SMB2 Write response message.
 *
 * This response contains information about the write operation,
 * including the number of bytes actually written.
 *
 * @author mbechler
 */
public class Smb2WriteResponse extends ServerMessageBlock2Response {

    private int count;
    private int remaining;

import jcifs.internal.util.SMBUtil;

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

    /**

    /**
     * SMB command for NT transaction operations.
     */
    public static final byte SMB_COM_NT_TRANSACT = (byte) 0xA0;

    /**
     * SMB command to cancel an NT operation.
     */
    public static final byte SMB_COM_NT_CANCEL = (byte) 0xA4;

    /**
     * SMB command for secondary NT transaction operations.
     */

# Renvoyer directement une réponse

Lorsque vous créez une *opération de chemins* **FastAPI**, vous pouvez normalement retourner n'importe quelle donnée : un `dict`, une `list`, un modèle Pydantic, un modèle de base de données, etc.

Par défaut, **FastAPI** convertirait automatiquement cette valeur de retour en JSON en utilisant le `jsonable_encoder` expliqué dans [JSON Compatible Encoder](../tutorial/encoder.md){.internal-link target=_blank}.

The normal (default) process, is as follows.

A `FastAPI` application (instance) has an `.openapi()` method that is expected to return the OpenAPI schema.

As part of the application object creation, a *path operation* for `/openapi.json` (or for whatever you set your `openapi_url`) is registered.

It just returns a JSON response with the result of the application's `.openapi()` method.

    @Override
    public void setUp() throws Exception {
        super.setUp();
        pingSearchEngineJob = new PingSearchEngineJob();
    }

    // Test normal operation with GREEN status and state change
    public void test_execute_greenStatusNoChange() {
        // Setup mock components
        SearchEngineClient searchEngineClient = new SearchEngineClient() {
            @Override

                    // Missing trailing slash -> should complain about directory ending
                    Arguments.of("smb://server/share", "/share", true),
                    // Not a server root -> invalid list operation
                    Arguments.of("smb://server/share/", "/share/", false));
        }

        @ParameterizedTest(name = "invalid path: {0}")
        @MethodSource("invalidShareEnumCases")

* All **automatically handled** by the framework.
* All the dependencies can require data from requests and **augment the path operation** constraints and automatic documentation.
* **Automatic validation** even for *path operation* parameters defined in dependencies.
* Support for complex user authentication systems, **database connections**, etc.

     * return 0 for streams connected to regular files. However, a
     * stream created from a Named Pipe this method will query the server using a
     * "peek named pipe" operation and return the number of available bytes
     * on the server.
     */
    @Override
    public int available() throws IOException {
        SmbNamedPipe pipe;
        TransPeekNamedPipe req;

import jcifs.internal.SMBProtocolDecodingException;

/**
 * Response for SMB1 TRANS_TRANSACT_NAMED_PIPE transaction.
 *
 * This response contains the data returned from the named pipe
 * after a transact operation (write then read) has been completed.
 */
public class TransTransactNamedPipeResponse extends SmbComTransactionResponse {

    private final byte[] outputBuffer;

    /**