}
    }

    @Nested
    @DisplayName("Integration Scenarios")
    class IntegrationTests {

        @Test
        @DisplayName("Should complete full connection lifecycle")
        void testFullConnectionLifecycle() throws Exception {
            // Given
            when(transportPool.getSmbTransport(context, TEST_HOST, DEFAULT_PORT, false, false)).thenReturn(transport);

        }
    }

    @Nested
    @DisplayName("Integration Tests")
    class IntegrationTests {

        @Test
        @DisplayName("Should handle complete copy operation with multiple chunks")
        void testCompleteCopyOperation() {
            // Given
            byte[] sourceKey = new byte[SOURCE_KEY_SIZE];
            for (int i = 0; i < SOURCE_KEY_SIZE; i++) {

        }
    }

    @Nested
    @DisplayName("Integration Tests")
    class IntegrationTests {

        @Test
        @DisplayName("Should handle complete lock request workflow")
        void testCompleteLockWorkflow() {
            // Setup complete request with multiple locks
            Smb2Lock[] locks = new Smb2Lock[] { new Smb2Lock(0L, 1024L, Smb2Lock.SMB2_LOCKFLAG_EXCLUSIVE_LOCK),

    .url("https://www.nytimes.com/")
    .build();
client.newCall(newYorkTimesRequest).enqueue(new Callback() {
  ...
});
```

Running this race over home WiFi shows the Times (`0002`) completes just slightly sooner than the Post (`0001`):

```
0001 https://www.washingtonpost.com/
0001 0.000 callStart
0002 https://www.nytimes.com/
0002 0.000 callStart
0002 0.010 dnsStart
0001 0.013 dnsStart

## Version 4.2.2

_2019-10-06_

 *  Fix: When closing a canceled HTTP/2 stream, don't send the `END_STREAM` flag. This could cause
    the server to incorrectly interpret the stream as having completed normally. This is most useful
    when a request body needs to cancel its own call.


## Version 4.2.1

_2019-10-02_

     <span style="background-color:#007166"><font color="#D3D7CF"> INFO </font></span>  Waiting for application startup.
     <span style="background-color:#007166"><font color="#D3D7CF"> INFO </font></span>  Application startup complete.
```

</div>

Es **ALTAMENTE recomendable** que escribas o copies el código, lo edites y lo ejecutes localmente.

You can define background tasks to be run *after* returning a response.

This is useful for operations that need to happen after a request, but that the client doesn't really have to be waiting for the operation to complete before receiving the response.

This includes, for example:

* Email notifications sent after performing an action:

            cleanupExecutor.shutdownNow();
            Thread.currentThread().interrupt();
        }

        // Log final statistics
        log.info("ResourceManager shutdown complete. Total allocated: {}, released: {}, leaks: {}, force cleaned: {}", totalAllocated.get(),
                totalReleased.get(), totalLeaks.get(), cleaned);
    }

    /**
     * Create a managed resource wrapper

        // When
        byte[] buffer = new byte[512];
        int written = request.writeBytesWireFormat(buffer, 0);

        // Then
        assertEquals(32, written);

        // Verify complete structure
        assertEquals(32, SMBUtil.readInt2(buffer, 0)); // StructureSize
        assertEquals(0x0001, SMBUtil.readInt2(buffer, 2)); // Flags
        assertEquals(8192, SMBUtil.readInt4(buffer, 4)); // OutputBufferLength

        }
    }

    @Nested
    @DisplayName("Integration Tests")
    class IntegrationTests {

        @Test
        @DisplayName("Should handle complete read request workflow")
        void testCompleteReadWorkflow() {
            // Setup complete request
            request.setFileId(testFileId);
            request.setPadding((byte) 1);
            request.setReadFlags(Smb2ReadRequest.SMB2_READFLAG_READ_UNBUFFERED);