4. The daemon runs the request, sending back data such as logging output or tooling API events and intermediate models while doing so.
5. The daemon sends the result back. For some requests, this might be a simple success/failure result, and for others this might also include a more complex object, such as a tooling API model.

    /**
     * Close the file
     *
     * @throws SmbException if an I/O error occurs during close
     */
    @Override
    void close() throws SmbException;

    /**
     * Read a single byte from the current position
     *
     * @return read byte, -1 if EOF
     * @throws SmbException if an I/O error occurs during read
     */
    int read() throws SmbException;

    /**

    /**
     * Closes the pool and all connections in it
     *
     * @return whether any transport was still in use
     *
     * @throws CIFSException if an error occurs during authentication
     *
     */
    boolean close() throws CIFSException;

    /**
     * Authenticate arbitrary credentials represented by the

    @CustomSize(maxKey = "form.admin.max.input.size")
    public String urls;

    /**
     * URL patterns to include during crawling.
     */
    @CustomSize(maxKey = "form.admin.max.input.size")
    public String includedUrls;

    /**
     * URL patterns to exclude during crawling.
     */
    @CustomSize(maxKey = "form.admin.max.input.size")
    public String excludedUrls;

    /**

      }
      return null
    }

    if (requestMethod != "GET") {
      // Don't cache non-GET responses. We're technically allowed to cache HEAD, QUERY and some
      // POST requests, but the complexity of doing so is high and the benefit is low.
      return null
    }

    if (response.hasVaryAll()) {
      return null
    }

    val entry = Entry(response)
    var editor: DiskLruCache.Editor? = null

* A bash script that runs the previous steps and then starts your application
    * You would still need a way to start/restart *that* bash script, detect errors, etc.

/// tip

I'll give you more concrete examples for doing this with containers in a future chapter: [FastAPI in Containers - Docker](docker.md).

///

## Resource Utilization { #resource-utilization }

MinIO server supports storage class in erasure coding mode. This allows configurable data and parity drives per object.

This page is intended as a summary of MinIO Erasure Coding. For a more complete explanation, see <https://docs.min.io/community/minio-object-store/operations/concepts/erasure-coding.html>.

## Overview

         * @param request the request data
         * @param exceptionList the list of exceptions that occurred during retries
         */
        void onRequestEnd(FaultTolerantClient client, RequestData request, List<Exception> exceptionList);

        /**
         * Called when an exception occurs during a request attempt.
         *
         * @param client the fault-tolerant client
         * @param request the request data

 * This class holds the server capabilities, configuration, and security
 * parameters received during SMB protocol negotiation.
 *
 * Stores server-specific data obtained during SMB1 protocol negotiation.
 */
public class ServerData {

    /**
     * Default constructor for ServerData.
     * Creates an empty server data container to be populated during SMB negotiation.
     */
    public ServerData() {
        // Default constructor

    /**
     * Gets the external profiles that were active during model building. External profiles are those that were
     * contributed by {@link ModelBuildingRequest#getProfiles()}.
     *
     * @return The active external profiles or an empty list if none, never {@code null}.
     */
    List<Profile> getActiveExternalProfiles();

    /**
     * Gets the problems that were encountered during the model building. Note that only problems of severity