Isso ainda é verdade.

Então, para poder ter **vários processos** ao mesmo tempo, tem que haver um **único processo escutando em uma porta** que então transmite a comunicação para cada processo de trabalho de alguma forma.

### Memória por Processo

Guillaume Nodet <******@****.***> 1725988727 +0200

        }
    }

    /**
     * Test rule processor chain behavior
     */
    public void test_ruleProcessorChain() {
        final List<String> executionOrder = new ArrayList<>();

        // Create custom processor that tracks execution
        ResponseProcessor processor = new ResponseProcessor() {
            @Override
            public void process(ResponseData responseData) {

    }

    @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;
    }

        }

        /**
         * Sets whether plugins should be processed during project building.
         * When true, the builder will process plugin information which may include
         * resolving plugin dependencies and executing plugin goals that participate in project building.
         *
         * @param processPlugins true if plugins should be processed, false otherwise
         * @return this builder instance
         */

A "middleware" is a function that works with every **request** before it is processed by any specific *path operation*. And also with every **response** before returning it.

* It takes each **request** that comes to your application.
* It can then do something to that **request** or run any needed code.
* Then it passes the **request** to be processed by the rest of the application (by some *path operation*).

        // 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...

```

### Monitoring

```java
// Monitor crawling progress
while (crawler.crawlerContext.getStatus() == CrawlerStatus.RUNNING) {
    int processed = dataService.getCount(sessionId);
    System.out.println("Processed: " + processed + " URLs");
    Thread.sleep(5000);
}
```

## Contributing

We welcome contributions to Fess Crawler! Please follow these guidelines:

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 {