byte[] buffer = createValidWriteResponse(1024, 512);

            int bytesRead = response.readBytesWireFormat(buffer, 0);

            assertEquals(16, bytesRead); // Structure size + reserved (4) + count (4) + remaining (4) + channel info (4)
            assertEquals(1024, response.getCount());
            assertEquals(512, response.getRemaining());
        }

        @Test

    /** Default response timeout in milliseconds */
    int DEFAULT_RESPONSE_TIMEOUT = 30000;
    /** Default socket timeout in milliseconds */
    int DEFAULT_SO_TIMEOUT = 35000;
    /** Default receive buffer size in bytes */
    int DEFAULT_RCV_BUF_SIZE = 60416;
    /** Default send buffer size in bytes */
    int DEFAULT_SND_BUF_SIZE = 16644;
    /** Default session limit */
    int DEFAULT_SSN_LIMIT = 250;

/// note | 📡 ℹ

`Request` ✔️ `request.scope` 🔢, 👈 🐍 `dict` ⚗ 🗃 🔗 📨.

 `Request` ✔️ `request.receive`, 👈 🔢 "📨" 💪 📨.

 `scope` `dict` & `receive` 🔢 👯‍♂️ 🍕 🔫 🔧.

 & 👈 2️⃣ 👜, `scope` & `receive`, ⚫️❔ 💪 ✍ 🆕 `Request` 👐.

💡 🌅 🔃 `Request` ✅ <a href="https://www.starlette.io/requests/" class="external-link" target="_blank">💃 🩺 🔃 📨</a>.

///

///

## Duplicate headers { #duplicate-headers }

It is possible to receive duplicate headers. That means, the same header with multiple values.

You can define those cases using a list in the type declaration.

You will receive all the values from the duplicate header as a Python `list`.

## Await for messages and send messages { #await-for-messages-and-send-messages }

In your WebSocket route you can `await` for messages and send messages.

{* ../../docs_src/websockets/tutorial001.py hl[48:52] *}

You can receive and send binary, text, and JSON data.

## Try it { #try-it }

If your file is named `main.py`, run your application with:

<div class="termy">

```console
$ fastapi dev main.py

description: Suggest an idea for this project
labels: [ "a:feature", "to-triage" ]
assignees: [ ]
body:
  - type: markdown
    attributes:
      value: |
        Please follow the instructions below.
        We receive dozens of issues every week, so to stay productive, we will close issues that don't provide enough information.

        Please open Android-related issues on [the Android Issue Tracker](https://source.android.com/source/report-bugs)

Channel communication is the main method of synchronization
between goroutines.  Each send on a particular channel
is matched to a corresponding receive from that channel,
usually in a different goroutine.
</p>

<p class="rule">
A send on a channel is synchronized before the completion of the
corresponding receive from that channel.
</p>

<p>
This program:
</p>

<pre>
var c = make(chan int, 10)
var a string

    private static final byte[] CONTEXT_NAME_BYTES = CONTEXT_NAME.getBytes();

    // The response structure is reserved and must be zero (8 bytes)
    private byte[] reserved = new byte[8];

    /**
     * Create a new durable handle response
     */
    public DurableHandleResponse() {
        // Reserved field initialized to zeros
    }

    @Override
    public byte[] getName() {
        return CONTEXT_NAME_BYTES;

Un `Request` también tiene un `request.receive`, que es una función para "recibir" el cuerpo del request.

El `dict` `scope` y la función `receive` son ambos parte de la especificación ASGI.

Y esas dos cosas, `scope` y `receive`, son lo que se necesita para crear una nueva *Request instance*.

        Optional<Integer> noMatch = findNtStatus(0xdeadbeef);
        assertFalse(noMatch.isPresent(), "Mapping for unknown code should be absent");
    }

    @Test
    @DisplayName("Mocked consumer receives correct NTSTATUS value")
    void testConsumerInteraction() {
        final int dosErr = 0x00010001;
        final int expectedNt = 0xc0000002;

        interface NtStatusConsumer {