{* ../../docs_src/request_files/tutorial001_an_py39.py hl[14] *}

Using `UploadFile` has several advantages over `bytes`:

* You don't have to use `File()` in the default value of the parameter.
* It uses a "spooled" file:
    * A file stored in memory up to a maximum size limit, and after passing this limit it will be stored in disk.

{* ../../docs_src/request_files/tutorial001_an_py39.py hl[14] *}

Utilizar `UploadFile` tem várias vantagens sobre `bytes`:

* Você não precisa utilizar o `File()` no valor padrão do parâmetro.
* Ele utiliza um arquivo "spooled":
    * Um arquivo armazenado na memória até um limite máximo de tamanho, e após passar esse limite, ele será armazenado no disco.

{* ../../docs_src/request_files/tutorial001_an_py39.py hl[14] *}

Usar `UploadFile` tiene varias ventajas sobre `bytes`:

* No tienes que usar `File()` en el valor por defecto del parámetro.
* Usa un archivo "spooled":
    * Un archivo almacenado en memoria hasta un límite de tamaño máximo, y después de superar este límite, se almacenará en el disco.

    return planConnectToRoute(newRouteSelection.next(), newRouteSelection.routes)
  }

  /**
   * Returns a plan to reuse a pooled connection, or null if the pool doesn't have a connection for
   * this address.
   *
   * If [planToReplace] is non-null, this will swap it for a pooled connection if that pooled
   * connection uses HTTP/2. That results in fewer sockets overall and thus fewer TCP slow starts.
   */

        PooledObject<TestComponent> pooled1 = factory.wrap(component);
        assertNotNull(pooled1);

        // Test wrapping same object multiple times
        PooledObject<TestComponent> pooled2 = factory.wrap(component);
        assertNotNull(pooled2);
        assertNotSame(pooled1, pooled2); // Different PooledObject instances
        assertSame(pooled1.getObject(), pooled2.getObject()); // Same wrapped object
    }

    @DisplayName("Should distinguish between pooled and non-pooled connections")
    void testPooledVsNonPooledConnections() {
        // When: Create pooled and non-pooled connections
        SmbTransportImpl pooled = pool.getSmbTransport(ctx, address, 445, false);
        SmbTransportImpl nonPooled = pool.getSmbTransport(ctx, address, 445, true);

        // Then: Pool should track pooled but not non-pooled

    /**
     * Wraps an object instance into a pooled object.
     * @param obj The object to wrap
     * @return A PooledObject wrapping the given object
     */
    @Override
    public PooledObject<T> wrap(final T obj) {
        return new DefaultPooledObject<>(obj);
    }

    /**
     * Destroys a pooled object and notifies the destroy listener if set.
     * @param p The pooled object to destroy

 *     list of available routes.
 *
 * If the pool gains an eligible connection while DNS, TCP, or TLS work is in flight, this finder
 * will prefer pooled connections. Only pooled HTTP/2 connections are used for such de-duplication.
 *
 * It is possible to cancel the finding process by canceling its call.
 *

        // Could implement a more sophisticated buffer pool here
    }

    /**
     * Clean up all pooled regions
     *
     * This method should be called when shutting down to
     * release all resources.
     */
    public void cleanup() {
        // Clean up all pooled regions
        RdmaMemoryRegion region;

        while ((region = availableSendRegions.poll()) != null) {

    // If we raced another call connecting to this host, coalesce the connections. This makes for
    // 3 different lookups in the connection pool!
    val pooled3 = routePlanner.planReusePooledConnection(this, routes)
    if (pooled3 != null) return pooled3.connection

    connection.withLock {
      connectionPool.put(connection)
      user.acquireConnectionNoEvents(connection)
    }