{* ../../docs_src/dependencies/tutorial005_an_py310.py hl[13] *}

Let's focus on the parameters declared:

* Even though this function is a dependency ("dependable") itself, it also declares another dependency (it "depends" on something else).
    * It depends on the `query_extractor`, and assigns the value returned by it to the parameter `q`.
* It also declares an optional `last_query` cookie, as a `str`.

# Configurer les chemins d'accès { #path-operation-configuration }

Vous pouvez passer plusieurs paramètres à votre *décorateur de chemin d'accès* pour le configurer.

/// warning | Alertes

Notez que ces paramètres sont passés directement au *décorateur de chemin d'accès*, et non à votre *fonction de chemin d'accès*.

///

## Définir le code d'état de la réponse { #response-status-code }

- path operations (plural): chemins d'accès
- path operation function: fonction de chemin d'accès
- path operation decorator: décorateur de chemin d'accès

- path parameter: paramètre de chemin
- query parameter: paramètre de requête

- the `Request`: `Request` (keep as code identifier)
- the `Response`: `Response` (keep as code identifier)

- deployment: déploiement
- to upgrade: mettre à niveau

     *
     * @param formParameters the form parameters
     */
    public void setFormParameters(final Map<String, String> formParameters) {
        this.formParameters = formParameters;
    }

    /**
     * NTLM-specific parameters (e.g., jcifs.* properties).
     * Used when authSchemeType is NTLM to configure the JCIFS engine.
     *
     * <p>Supported parameters include:</p>

    //                                     Parameter Logging
    //                                     -----------------
    // logging filter cannot show the parameters when multi-part so logging here
    protected void showFieldLoggingTitle() {
        if (logger.isDebugEnabled()) {
            logger.debug("[Multipart Request Parameter]");
        }
    }

# Cookies de Resposta { #response-cookies }

## Use um parâmetro `Response` { #use-a-response-parameter }

Você pode declarar um parâmetro do tipo `Response` na sua *função de operação de rota*.

E então você pode definir cookies nesse objeto de resposta *temporário*.

{* ../../docs_src/response_cookies/tutorial002_py310.py hl[1, 8:9] *}

## Using `BackgroundTasks` { #using-backgroundtasks }

First, import `BackgroundTasks` and define a parameter in your *path operation function* with a type declaration of `BackgroundTasks`:

{* ../../docs_src/background_tasks/tutorial001_py310.py hl[1,13] *}

**FastAPI** will create the object of type `BackgroundTasks` for you and pass it as that parameter.

## Create a task function { #create-a-task-function }

import java.lang.annotation.Target;

/**
 * Marks a method as an event subscriber.
 *
 * <p>The type of event will be indicated by the method's first (and only) parameter, which cannot
 * be primitive. If this annotation is applied to methods with zero parameters, or more than one
 * parameter, the object containing the method will not be able to register for event delivery from
 * the {@link EventBus}.
 *

        default:
            return "Unknown error: 0x" + Integer.toHexString(returnCode);
        }
    }

    /**
     * Encodes the witness RPC message parameters to NDR format.
     * Subclasses must implement this method to encode their specific parameters.
     *
     * @param buf the NDR buffer to encode into
     * @throws NdrException if encoding fails
     */

        // Setup - verify parameter order is correct
        final VaMessenger<FessMessages> messageCode = messages -> messages.addErrorsInvalidQueryUnknown(UserMessages.GLOBAL_PROPERTY_KEY);
        final String message = "Parameter order test";
        final Exception cause = new RuntimeException("Test cause");

        // Execute with three parameters