* `close()`: Cierra el archivo.

Como todos estos métodos son métodos `async`, necesitas "await" para ellos.

Por ejemplo, dentro de una *path operation function* `async` puedes obtener los contenidos con:

```Python
contents = await myfile.read()
```

Si estás dentro de una *path operation function* normal `def`, puedes acceder al `UploadFile.file` directamente, por ejemplo:

```Python
contents = myfile.file.read()
```

            result = buf.dec_ndr_long();
        } else { /* Bind_ack or Response */
            decode_out(buf);
        }
    }

    /**
     * Get the operation number for this DCERPC message.
     * @return the operation number
     */
    public abstract int getOpnum();

    /**
     * Encode the input parameters for this DCERPC message.
     * @param buf the buffer to encode into

    end
    dep ->> operation: Executar dependência, e.g. sessão de BD
    opt raise
        operation -->> dep: Lançar exceção (e.g. HTTPException)
        opt handle
            dep -->> dep: Pode capturar exceções, lançar uma nova HTTPException, lançar outras exceções
        end
        handler -->> client: resposta de erro HTTP
    end

    operation ->> client: Retornar resposta ao cliente

        // Verify counters
        assertEquals(1, stats.getRdmaReads(), "Should have 1 read operation");
        assertEquals(1, stats.getRdmaWrites(), "Should have 1 write operation");
        assertEquals(1, stats.getRdmaSends(), "Should have 1 send operation");
        assertEquals(1, stats.getRdmaReceives(), "Should have 1 receive operation");
        assertEquals(5120, stats.getBytesTransferred(), "Should have transferred 5KB total");

            assertArrayEquals(new byte[] { 1, 2, 3, 4 }, handle.getSessionKey());
        }
    }

    @Nested
    @DisplayName("Bind Operation Tests")
    class BindOperationTests {

        @Test
        @DisplayName("Should execute bind operation successfully")
        void testBindSuccess() throws DcerpcException, IOException {
            // Given: Spy to intercept sendrecv calls

## Usa el objeto `Request` directamente

Imaginemos que quieres obtener la dirección IP/host del cliente dentro de tu *path operation function*.

Para eso necesitas acceder al request directamente.

{* ../../docs_src/using_request_directly/tutorial001.py hl[1,7:8] *}

Al declarar un parámetro de *path operation function* con el tipo siendo `Request`, **FastAPI** sabrá pasar el `Request` en ese parámetro.

/// tip | Consejo

 *
 * @author mbechler
 */
public class Smb2ReadRequest extends ServerMessageBlock2Request<Smb2ReadResponse> implements RequestWithFileId {

    /**
     * Flag to indicate unbuffered read operation
     */
    public static byte SMB2_READFLAG_READ_UNBUFFERED = 0x1;
    /**
     * Channel type for standard read without RDMA
     */
    public static int SMB2_CHANNEL_NONE = 0x0;
    /**

import java.io.IOException;

import jcifs.smb1.smb1.ACE;
import jcifs.smb1.smb1.SecurityDescriptor;

/**
 * MS-RPC share information retrieval operation.
 *
 * This class implements the Server Service (SRVSVC) ShareGetInfo operation
 * for retrieving detailed information about a network share, including
 * security descriptors.
 */
public class MsrpcShareGetInfo extends srvsvc.ShareGetInfo {

    /**

which in turn are made up of memory operations.
</p>

<p>
A <i>memory operation</i> is modeled by four details:
</p>
<ul>
	<li>its kind, indicating whether it is an ordinary data read, an ordinary data write,
    or a <i>synchronizing operation</i> such as an atomic data access,
	a mutex operation, or a channel operation,</li>
	<li>its location in the program,</li>

///

This parameter doesn't create that endpoint / *path operation*, but declares that the URL `/token` will be the one that the client should use to get the token. That information is used in OpenAPI, and then in the interactive API documentation systems.

We will soon also create the actual path operation.

/// info