CompletableFuture<Void> future = CompletableFuture.runAsync(() -> {
            while (handle.isActive()) {
                try {
                    // Note: Actual SMB2 Change Notify implementation would go here
                    // For now, this is a placeholder that simulates monitoring

                    // In a real implementation, we would:

        block.uid = 0x1234;
        block.useUnicode = true;

        byte[] buf = new byte[256];
        int n = block.writeAndXWireFormat(buf, 0);

        assertTrue(n > 0);
        // Note: In actual implementation, uid is NOT propagated for non-AndX SMBs
        // uid is only set for AndXServerMessageBlock instances (line 167 in AndXServerMessageBlock.java)
        // Only useUnicode is set before the instanceof check (line 149)

# Obter Usuário Atual { #get-current-user }

No capítulo anterior, o sistema de segurança (que é baseado no sistema de injeção de dependências) estava fornecendo à *função de operação de rota* um `token` como uma `str`:

{* ../../docs_src/security/tutorial001_an_py39.py hl[12] *}

Mas isso ainda não é tão útil.

Vamos fazer com que ele nos forneça o usuário atual.

## Criar um modelo de usuário { #create-a-user-model }

 *
 * Note: This is a skeleton implementation. A real implementation would
 * require proper DiSNI integration with actual RDMA hardware.
 */
public class DisniRdmaConnection extends RdmaConnection {

    private static final Logger log = LoggerFactory.getLogger(DisniRdmaConnection.class);

    // DiSNI objects - would be actual DiSNI types in real implementation
    private final Object endpoint; // RdmaActiveEndpoint

        assertEquals(35000, SmbConstants.DEFAULT_CONN_TIMEOUT);
        // Note: USE_UNICODE and FORCE_UNICODE don't exist in the interface
        // These tests should be removed or replaced with actual constants
    }

    /**
     * Test individual FLAGS2 constants.
     */
    @Test
    @DisplayName("FLAGS2 individual constants are correct")
    void flags2ConstantsTest() {

        handlers.clear();
    }

    /**
     * Pre-populates the protocol handlers cache with mock handlers for testing.
     * This avoids the need for actual protocol handlers to be available.
     */
    private void setupMockProtocolHandlers() throws Exception {
        Field handlersField = Handler.class.getDeclaredField("PROTOCOL_HANDLERS");

    void toString_rendersHex(byte[] input, String expected) {
        // Arrange
        SecurityBlob blob = new SecurityBlob(input);

        // Act
        String actual = blob.toString();

        // Assert
        assertEquals(expected, actual, "Hex string should match expected format");
    }

    // Ensures a default-constructed blob starts empty and stable across APIs
    @Test

    assertThat(body.byteString()).isEqualTo(ByteString.EMPTY)
  }

  @Test
  fun byteStringSeesBom() {
    val body = body("efbbbf68656c6c6f")
    val actual = body.byteString()
    val expected: ByteString = "efbbbf68656c6c6f".decodeHex()
    assertThat(actual).isEqualTo(expected)
  }

  @Test
  fun byteStringClosesUnderlyingSource() {
    val closed = AtomicBoolean()
    val body: ResponseBody =

          <type>DOM</type>
          <description>
            Toolchain identification information, which will be matched against project requirements.
            &lt;p>Actual content structure is completely open: each toolchain type will define its own format and
            semantics.
            &lt;p>This is generally a properties format: {@code &lt;name&gt;value&lt;/name&gt;} with predefined

        });

        // Note: here, type decides is artifact added to "build path" (for example during resolution)
        // and "build path" is intermediate data that is used to create actual Java classpath/modulepath
        // but to create those, proper filtering should happen via Type properties.
    }

    @Override
    public void addHandlers(Map<String, ArtifactHandler> handlers) {