- [ ] Add persistent handle capability negotiation
- [ ] Create handle cache for reconnection

#### 2.3 Integration Points
- Extend `SmbFile` with persistent handle support
- Modify `SmbSession` for handle replay during reconnection
- Update `Smb2CreateRequest/Response` for durable contexts

---

### Phase 3: Multi-Channel Support
**Priority: MEDIUM** | **Estimated Effort: 5-6 weeks**

                }
            }, "SmbSession should work with try-with-resources");

            verify(mockSession, times(1)).close();
        }

        @Test
        @DisplayName("Should handle exceptions during resource cleanup")
        void shouldHandleExceptionsDuringResourceCleanup() throws Exception {
            SmbSession mockSession = mock(SmbSession.class);

        block.digest = digest;

        byte[] buf = new byte[256];
        int len = block.encode(buf, 0);

        assertTrue(len > 0);
        assertTrue(digest.called, "sign() should be called during encode");
        assertEquals(len, digest.lastLength);
    }

    @Test
    @DisplayName("writeAndXWireFormat without andx writes 0xFF and sentinel offset")
    void testWriteAndXWireFormatWithoutAndx() {

                assertEquals("Structure size != 4", exception.getMessage());
            }
        }
    }

    @Test
    @DisplayName("Should not modify buffer during write operation")
    void testWriteDoesNotModifyBuffer() {
        // Given
        byte[] buffer = new byte[256];
        // Fill buffer with test pattern
        for (int i = 0; i < buffer.length; i++) {

     */
    protected abstract void doReceiveFragment(byte[] buf, boolean isDirect) throws IOException;

    /**
     * Closes this DCERPC handle and releases resources
     * @throws IOException if an I/O error occurs during close
     */
    public abstract void close() throws IOException;

> http://host2/export8
```

*A noticeable trait of this expansion is that it chooses unique hosts such the setup provides maximum protection and availability.*

- Choosing an erasure set for the object is decided during `PutObject()`, object names are used to find the right erasure set using the following pseudo code.

```go
// hashes the key returning an integer.
func sipHashMod(key string, cardinality int, id [16]byte) int {

				jt.Take()
				go healEntry(bucket, *entry)
			},
			finished: func(errs []error) {
				success := countErrs(errs, nil)
				if success < len(disks)/2+1 {
					retErr = fmt.Errorf("one or more errors reported during listing: %v", errors.Join(errs...))
				}
			},
		})
		jt.Wait() // synchronize all the concurrent heal jobs
		if err != nil {
			// Set this such that when we return this function

   * up the necessary in-memory cache information.
   *
   * The initialization time may vary depending on the journal file size and the current actual
   * cache size. The application needs to be aware of calling this function during the
   * initialization phase and preferably in a background worker thread.
   *
   * Note that if the application chooses to not call this method to initialize the cache. By

And it will work and will be useful **during development**.

But if your connection to the server is lost, the **running process** will probably die.

### Instrumentation