Bu hâlâ geçerli.

Dolayısıyla **aynı anda birden fazla process** çalıştırabilmek için, **port** üzerinde dinleyen **tek bir process** olmalı ve bu process iletişimi bir şekilde worker process'lere aktarmalıdır.

### Process Başına Bellek { #memory-per-process }

import org.codelibs.fess.crawler.extractor.Extractor;
import org.codelibs.fess.crawler.extractor.impl.TikaExtractor;
import org.codelibs.fess.crawler.processor.ResponseProcessor;
import org.codelibs.fess.crawler.processor.impl.DefaultResponseProcessor;
import org.codelibs.fess.crawler.rule.Rule;
import org.codelibs.fess.crawler.rule.RuleManager;
import org.codelibs.fess.crawler.serializer.DataSerializer;

1. What version of Go are you using (`go version`)?
2. What operating system and processor architecture are you using?
3. What did you do?
4. What did you expect to see?
5. What did you see instead?

For change proposals, see [Proposing Changes To Go](https://go.dev/s/proposal-process).

## Contributing code

          "name": "TestDistribution"
        }
      },
      {
        "subprojects": [
          "build-cache-example-client",
          "build-process-services",
          "configuration-cache-base",
          "files",
          "internal-instrumentation-processor",
          "kotlin-dsl-plugins",
          "kotlin-dsl-provider-plugins",
          "language-native",
          "testing-jvm-infrastructure",

* **Ejecutarse como un servidor** (al menos durante el proceso de adquisición del certificado) en la dirección IP pública asociada con el dominio.
    * Como dijimos anteriormente, solo un proceso puede estar escuchando en una IP y puerto específicos.
    * Esta es una de las razones por las que es muy útil cuando el mismo TLS Termination Proxy también se encarga del proceso de renovación del certificado.

        try {
            this.threadPool = null;
            final RequestProcessor processor = new RequestProcessor(encoding, threshold);
            connect(processor, e -> {
                throw new CurlException("Failed to process a request.", e);
            });
            return processor.getResponse();
        } finally {
            this.threadPool = originalThreadPool;
        }
    }

Assim, ela envia o primeiro item, o cliente o recebe e começa a processá-lo, enquanto você ainda pode estar produzindo o próximo item.

```mermaid
sequenceDiagram
    participant App
    participant Client

    App->>App: Produce Item 1
    App->>Client: Send Item 1
    App->>App: Produce Item 2
    Client->>Client: Process Item 1
    App->>Client: Send Item 2
    App->>App: Produce Item 3

    "crossVersionTests": false
  },
  {
    "name": "process-memory-services",
    "path": "platforms/core-runtime/process-memory-services",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "process-services",
    "path": "platforms/core-runtime/process-services",
    "unitTests": true,
    "functionalTests": true,

     * @param query the Lucene query to be processed
     * @param boost the boost factor to apply to the query
     * @return the processed OpenSearch QueryBuilder
     */
    public QueryBuilder execute(final QueryContext context, final Query query, final float boost) {
        return filterChain.execute(context, query, boost);
    }

    /**
     * Adds a query command to the processor.
     *

# Extender OpenAPI { #extending-openapi }

Hay algunos casos en los que podrías necesitar modificar el esquema de OpenAPI generado.

En esta sección verás cómo hacerlo.

## El proceso normal { #the-normal-process }

El proceso normal (por defecto) es el siguiente.

Una aplicación (instance) de `FastAPI` tiene un método `.openapi()` que se espera que devuelva el esquema de OpenAPI.