bb.putShort((short) 76); // nodeOffset

        // Path string at offset 22 (relative to start of referral at position 0)
        bb.position(22);
        String path = "\\\\server\\share";
        bb.put(path.getBytes(StandardCharsets.UTF_16LE));
        bb.putShort((short) 0);

        // Alt path string at offset 54
        bb.position(54);
        String altPath = "\\\\alt\\path";

        // Assert cause propagation
        assertSame(mockCause, ex.getCause(), "Cause should be exactly the provided instance");

        // Access common Throwable methods to exercise paths without touching the cause
        assertNotNull(ex.toString(), "toString should be non-null");
        ex.getMessage(); // don't assert content to avoid implementation assumptions

    * Pero te proporciona las herramientas para construir aplicaciones web sencillas, con enrutamiento basado en paths, etc.
    * Si estás comparando Starlette, compáralo con Sanic, Flask, Django, etc. Frameworks web (o microframeworks).
* **FastAPI**:

        Path mavenConf = mavenHome.resolve("conf");
        Files.createDirectories(mavenConf);
        Path mavenUserProps = mavenConf.resolve("maven-user.properties");
        Files.writeString(mavenUserProps, "${includes} = ?${session.rootDirectory}/.mvn/maven-user.properties\n");
        Path rootDirectory = fs.getPath("C:\\myRootDirectory");
        Path topDirectory = rootDirectory.resolve("myTopDirectory");

### Paso 3: crea una *path operation* { #step-3-create-a-path-operation }

#### Path { #path }

"Path" aquí se refiere a la última parte de la URL empezando desde la primera `/`.

Así que, en una URL como:

```
https://example.com/items/foo
```

...el path sería:

```
/items/foo
```

/// info | Información

Un "path" también es comúnmente llamado "endpoint" o "ruta".

     *
     * @return the transport pool
     */
    SmbTransportPool getTransportPool();

    /**
     * Get the DFS resolver for handling distributed file system paths
     *
     * @return the DFS instance for this context
     */
    DfsResolver getDfs();

    /**
     * Get the SID resolver for resolving security identifiers
     *

    assert response.status_code == 200, response.text
    assert response.json() == {
        "openapi": "3.1.0",
        "info": {"title": "FastAPI", "version": "0.1.0"},
        "paths": {
            "/login": {
                "post": {
                    "responses": {
                        "200": {
                            "description": "Successful Response",

### Passo 3: crie uma operação de rota { #step-3-create-a-path-operation }

#### Path { #path }

"Path" aqui se refere à última parte da URL, começando do primeiro `/`.

Então, em uma URL como:

```
https://example.com/items/foo
```

...o path seria:

```
/items/foo
```

/// info | Informação

Um "path" também é comumente chamado de "endpoint" ou de "rota".

///

   "/${TARGET}/usr/lib64"
;;
esac

# Link in architecture specific includes from the system; note that we cannot
# link in the whole x86_64-linux-gnu folder, as otherwise we're overlaying
# system gcc paths that we do not want to find.
# TODO(klimek): Automate linking in all non-gcc / non-kernel include
# directories.
mkdir -p "/${TARGET}/usr/include/x86_64-linux-gnu"

                "'\\server\\share\\path', 'server', 'share', 'path'",
                "'\\server\\share\\path\\file.txt', 'server', 'share', 'path\\file.txt'",
                "'\\server.domain.com\\share\\deep\\path\\structure', 'server.domain.com', 'share', 'deep\\path\\structure'" })
        @DisplayName("Should split DFS paths correctly")