baos.write(new byte[8]);

            // SERVER_CHECKSUM data
            writeLittleEndianInt(baos, PacSignature.KERB_CHECKSUM_HMAC_MD5);
            baos.write(mockChecksum);

            // Padding to align
            while (baos.size() < 104) {
                baos.write(0);
            }

            // PRIVSVR_CHECKSUM data
            writeLittleEndianInt(baos, PacSignature.KERB_CHECKSUM_HMAC_MD5);

        protected int fromHours;

        /** Starting minute of the interval */
        protected int fromMinutes;

        /** Ending hour of the interval */
        protected int toHours;

        /** Ending minute of the interval */
        protected int toMinutes;

        /** Delay in milliseconds to apply during this interval */
        protected long delay;

        That's a lot of work they are doing, but if more FastAPI users came to help others like them just a little bit more, it would be much less effort for them (and you and me 😅).

        assertEquals((byte) 0x00, getPrivateField(cmd, "maxSetupCount"));
        assertEquals(4096, getPrivateField(cmd, "maxDataCount"));
    }

    @Test
    @DisplayName("writeSetupWireFormat writes subCommand and padding")
    void testWriteSetup() throws Exception {
        Trans2GetDfsReferral cmd = new Trans2GetDfsReferral("foo");
        byte[] buf = new byte[2];
        int r = cmd.writeSetupWireFormat(buf, 0);

Up to now, you have been declaring the parts of the request that you need with their types.

Taking data from:

* The path as parameters.
* Headers.
* Cookies.
* etc.

And by doing so, **FastAPI** is validating that data, converting it and generating documentation for your API automatically.

But there are situations where you might need to access the `Request` object directly.

      <version>4.13.2</version>
    </dependency>
    <dependency>
      <!--
      Do not include Truth in non-test scope! Doing so creates a problematic dependency cycle.
      -->
      <groupId>com.google.truth</groupId>
      <artifactId>truth</artifactId>
      <version>${truth.version}</version>
      <scope>test</scope>
      <exclusions>

      <version>4.13.2</version>
    </dependency>
    <dependency>
      <!--
      Do not include Truth in non-test scope! Doing so creates a problematic dependency cycle.
      -->
      <groupId>com.google.truth</groupId>
      <artifactId>truth</artifactId>
      <version>${truth.version}</version>
      <scope>test</scope>
      <exclusions>

        if (i < len) {
            System.arraycopy(input, offset + i, buffer, bufferNdx, len - i);
        }
    }

    /**
     * Completes the hash computation by performing final operations such
     * as padding. At the return of this engineDigest, the MD engine is
     * reset.
     *
     * @return the array of bytes for the resulting hash value.
     */
    @Override
    public byte[] engineDigest() {

        int srcIndex = 0;

        // Simulate groupName = false (0x00), nodeType = 0 (0x00) -> src[srcIndex] = 0x00
        src[srcIndex] = (byte) 0x00;
        src[srcIndex + 1] = (byte) 0x00; // Reserved/padding byte

        // Simulate address = 192.168.1.1 (0xC0A80101)
        src[srcIndex + 2] = (byte) 0xC0;
        src[srcIndex + 3] = (byte) 0xA8;
        src[srcIndex + 4] = (byte) 0x01;

#### Shared reader thread

We can't rely on application threads to read data from the socket. Application threads are transient: sometimes they're reading and writing and sometimes they're off doing application-layer things. But the socket is permanent, and it needs constant attention: we dispatch all incoming frames so the connection is good-to-go when the application layer needs it.