return getInput().readDirect(buf, off, len);

    }

    @Override
    public void send(final byte[] buf, final int off, final int length) throws IOException {
        getOutput().writeDirect(buf, off, length, 1);
    }

    /**
     *
     * {@inheritDoc}
     *
     * @see jcifs.smb.SmbPipeHandleInternal#getPipeType()
     */

     * @param b the buffer to read into
     * @param off the offset in the buffer to start writing
     * @param len the number of bytes to read
     * @return number of bytes read
     * @throws IOException if an I/O error occurs
     */
    public static int readn(final InputStream in, final byte[] b, final int off, final int len) throws IOException {
        int i = 0, n = -5;

        if (off + len > b.length) {

        int len = this.length;

        if (this.next != null) {
            final int nextStart = dstIndex;
            dstIndex += this.next.encode(dst, dstIndex);
            final int off = nextStart - start;
            SMBUtil.writeInt4(off, dst, start + 20);
            len += dstIndex - nextStart;
        }

        if (this.digest != null) {
            this.digest.sign(dst, this.headerStart, this.length, this, getResponse());

the renewal program to acquire the certificates, then configure them with the TLS Termination Proxy, and then restart the TLS Termination Proxy. This is not ideal, as your app(s) will not be available during the time that the TLS Termination Proxy is off.

All this renewal process, while still serving the app, is one of the main reasons why you would want to have a **separate system to handle HTTPS** with a TLS Termination Proxy instead of just using the TLS certificates with the application...

                    log.debug("Logging off session on " + trans);
                }

                this.netbiosName = null;

                synchronized (this.trees) {
                    long us = this.usageCount.get();
                    if ((inUse ? us != 1 : us > 0)) {
                        log.warn("Logging off session while still in use " + this + ":" + this.trees);

If you are using **Kubernetes** (or others) and you are already setting **replication** at the cluster level, with multiple **containers**. In those cases, you are better off **building an image from scratch** as described above: [Build a Docker Image for FastAPI](#build-a-docker-image-for-fastapi).

And if you need to have multiple workers, you can simply use the `--workers` command line option.