@Override
    public SmbRandomAccessFile openRandomAccess(final String mode, final int sharing) throws SmbException {
        return new SmbRandomAccessFile(this, mode, sharing, false);
    }

    private void processAces(final ACE[] aces, final boolean resolveSids) throws IOException {
        String server = this.fileLocator.getServerWithDfs();
        int ai;

        if (resolveSids) {

     */
    @Override
    public OutputStream getOutputStream() throws IOException {
        return new SmbFileOutputStream(this);
    }

    private void processAces(final ACE[] aces, final boolean resolveSids) throws IOException {
        final String server = getServerWithDfs();
        int ai;

        if (resolveSids) {
            final SID[] sids = new SID[aces.length];

* Others...

## Replication - Processes and Memory { #replication-processes-and-memory }

With a FastAPI application, using a server program like the `fastapi` command that runs Uvicorn, running it once in **one process** can serve multiple clients concurrently.

But in many cases, you will want to run several worker processes at the same time.

### Multiple Processes - Workers { #multiple-processes-workers }

### Containers with Multiple Processes and Special Cases { #containers-with-multiple-processes-and-special-cases }

Of course, there are **special cases** where you could want to have **a container** with several **Uvicorn worker processes** inside.

In those cases, you can use the `--workers` command line option to set the number of workers that you want to run:

* Restarts
* **Replication (the number of processes running)**
* Memory
* Previous steps before starting

Up to this point, with all the tutorials in the docs, you have probably been running a **server program**, for example, using the `fastapi` command, that runs Uvicorn, running a **single process**.

            fail("Should throw JobProcessingException");
        } catch (JobProcessingException e) {
            assertTrue(e.getMessage().contains("10 crawler processes are running"));
            assertTrue(e.getMessage().contains("Max processes are 5"));
        }
    }

    // Test execute method with no max process limit
    public void test_execute_noMaxProcessLimit() {
        // Setup test

     */
    @JvmStatic
    @JvmName("enqueue")
    fun Call.enqueueEventSource(listener: EventSourceListener): EventSource = RealEventSource(this, listener).also(this::enqueue)

    /**
     * Processes the existing response with [listener].
     */
    @JvmStatic
    @JvmName("process")
    fun Response.processEventSource(listener: EventSourceListener) = RealEventSource(this, listener).processResponse(this)
  }

                }

            } catch (Exception e) {
                log.error("Error during witness unregistration", e);
            }
        });
    }

    /**
     * Processes a received witness notification.
     *
     * @param notification the notification to process
     */
    public void processNotification(WitnessNotification notification) {

     * Continuously processes crawled documents from the data service, transforms them,
     * and updates the search index until crawling is finished and all documents are processed.
     *
     * <p>The method performs the following operations in a loop:
     * <ul>
     * <li>Retrieves access results from the data service</li>
     * <li>Processes each document through transformers</li>

### TLS with SNI Extension { #tls-with-sni-extension }

**Only one process** in the server can be listening on a specific **port** in a specific **IP address**. There could be other processes listening on other ports in the same IP address, but only one for each combination of IP address and port.

TLS (HTTPS) uses the specific port `443` by default. So that's the port we would need.