- Update change notification handling

---

### Phase 5: RDMA (SMB Direct) Support
**Priority: LOW** | **Estimated Effort: 8-10 weeks**

RDMA provides high-speed, low-latency data transfer for supported network adapters.

#### 5.1 Core RDMA Infrastructure
```
Package: jcifs.internal.smb2.rdma
├── RdmaTransport.java           - RDMA transport implementation
├── RdmaCapability.java          - RDMA capability detection

- **Builder Pattern** - `CopyOptions` for configuring bean copying operations with fluent API
- **Adapter Pattern** - Logging adapters (`JclLoggerAdapter`, `JulLoggerAdapter`) for different logging frameworks
- **Template Method** - Resource traversal utilities with customizable handlers

        assertNotNull(r1, "First adapted resource must not be null");
        // For workgroup/server entries, names end with '/'
        assertTrue(r1.getName().endsWith("/"), "Name should end with '/'");

        assertTrue(itr.hasNext(), "Should have second element ready");
        SmbResource r2 = itr.next();
        assertNotNull(r2, "Second adapted resource must not be null");

    }

    @Test
    @DisplayName("Adapter throwing MalformedURLException on all entries")
    void adapterThrowsOnAllEntries() {
        // Setup
        FileEntry entry1 = mock(FileEntry.class);
        FileEntry entry2 = mock(FileEntry.class);

        when(delegate.hasNext()).thenReturn(true, true, false);
        when(delegate.next()).thenReturn(entry1, entry2);

        // Adapter that always throws

## In a hurry? { #in-a-hurry }

If you don't care about any of these terms and you just need to add security with authentication based on username and password *right now*, skip to the next chapters.

## OAuth2 { #oauth2 }

OAuth2 is a specification that defines several ways to handle authentication and authorization.

It is quite an extensive specification and covers several complex use cases.

/// tip

All this might seem contrived. And it might not be very clear how is it useful yet.

These examples are intentionally simple, but show how it all works.

In the chapters about security, there are utility functions that are implemented in this same way.

If you understood all this, you already know how those utility tools for security work underneath.

    /**
     * Unwrap the referral data to a specific implementation type
     *
     * @param <T> the target type to unwrap to
     * @param type the class of the target type
     * @return the referral adapted to type
     * @throws ClassCastException
     *             if the type is not valid for this object
     */
    <T extends DfsReferralData> T unwrap(Class<T> type);

    /**

/// tip

All this might not seem as useful with these simple examples.

But you will see how useful it is in the chapters about **security**.

And you will also see the amounts of code it will save you.

By considering these concepts, you will be able to **evaluate and design** the best way to deploy **your own APIs**.

In the next chapters, I'll give you more **concrete recipes** to deploy FastAPI applications.

But for now, let's check these important **conceptual ideas**. These concepts also apply to any other type of web API. 💡

import okhttp3.internal.platform.Platform
import okio.BufferedSink
import okio.BufferedSource
import okio.ForwardingSink
import okio.ForwardingSource
import okio.asOkioSocket
import okio.buffer

/**
 * Adapts a [java.net.Socket] to MockWebServer's needs.
 *
 * Note that [asOkioSocket] returns a socket that closes the underlying [java.net.Socket] when both
 * of its component streams are closed. This class takes advantage of that.
 */