}

    @Override
    public ResponseProcessor getResponseProcessor() {
        return responseProcessor;
    }

    /**
     * Sets the response processor for this rule.
     *
     * @param responseProcessor the response processor to set
     */
    public void setResponseProcessor(final ResponseProcessor responseProcessor) {
        this.responseProcessor = responseProcessor;
    }

```

</div>

////

A única opção nova aqui é `--workers` informando ao Uvicorn para iniciar 4 processos de trabalho.

Você também pode ver que ele mostra o **PID** de cada processo, `27365` para o processo pai (este é o **gerenciador de processos**) e um para cada processo de trabalho: `27368`, `27369`, `27370` e `27367`.

## Conceitos de Implantação

        // Initial state
        assertNull(testRule.getResponseProcessor());

        // Set response processor
        TestResponseProcessor processor = new TestResponseProcessor();
        testRule.setResponseProcessor(processor);
        assertSame(processor, testRule.getResponseProcessor());

        // Change response processor
        TestResponseProcessor newProcessor = new TestResponseProcessor();

process-ram.drawio.svg...

        }
    }

    /**
     * Processes allowed SIDs (Security Identifiers) and adds them to the SID set.
     * If the SID is a group, it recursively processes all group members.
     *
     * @param file the SMB1 file
     * @param sid the SID to process
     * @param sidSet the set of SIDs to add to
     */

### Múltiples Procesos - Un Ejemplo

En este ejemplo, hay un **Proceso Administrador** que inicia y controla dos **Worker Processes**.

Este Proceso Administrador probablemente sería el que escuche en el **puerto** en la IP. Y transmitirá toda la comunicación a los worker processes.

<font color="#4E9A06">INFO</font>:     Started parent process [<font color="#34E2E2"><b>27365</b></font>]
<font color="#4E9A06">INFO</font>:     Started server process [<font color="#06989A">27368</font>]
<font color="#4E9A06">INFO</font>:     Waiting for application startup.
<font color="#4E9A06">INFO</font>:     Application startup complete.
<font color="#4E9A06">INFO</font>:     Started server process [<font color="#06989A">27369</font>]

import org.codelibs.fess.crawler.processor.ResponseProcessor;

/**
 * The Rule interface defines the contract for implementing rules that can be applied to
 * response data in a web crawler. Implementations of this interface should provide logic
 * to determine if a given response data matches the rule, retrieve the rule's identifier,
 * and obtain the associated response processor.
 */
public interface Rule extends Serializable {

    /**
     * Artifact type name for a JAR file that can be placed either on the annotation processor class path
     * or module path. The path (classes or modules) is chosen by the plugin, possibly using heuristic rules.
     */
    String PROCESSOR = "processor";

    /**
     * Artifact type name for a JAR file to unconditionally place on the annotation processor class path.
     * If the JAR is modular, its module information are ignored.
     */

* mount (verb): montar
* statement (as in code statement): statement (do not translate to "declaración" or "sentencia")
* worker process: worker process (do not translate to "proceso trabajador" or "proceso de trabajo")
* worker processes: worker processes (do not translate to "procesos trabajadores" or "procesos de trabajo")
* worker: worker (do not translate to "trabajador")