This platform is agnostic to what exactly the purpose of the work is.
It might be creating an application, setting up development environments, orchestrating deployments, running simulations, etc.

This platform does not provide special support for a particular kind of automation. This is the responsibility of other platforms.

It is made up of 3 architecture modules:

## Zusatzfunktionen { #additional-features }

Das Haupt-[Tutorial – Benutzerhandbuch](../tutorial/index.md){.internal-link target=_blank} sollte ausreichen, um Ihnen einen Überblick über alle Hauptfunktionen von **FastAPI** zu geben.

In den nächsten Abschnitten sehen Sie weitere Optionen, Konfigurationen und zusätzliche Funktionen.

/// tip | Tipp

Die nächsten Abschnitte sind **nicht unbedingt „fortgeschritten“**.

        assertEquals(0, result);
    }

    /**
     * Test writeBytesWireFormat.
     */
    @Test
    void testWriteBytesWireFormat() {
        // Assuming path is ASCII and does not use unicode
        String dirName = "\testDir";
        SmbComDeleteDirectory sdd = new SmbComDeleteDirectory(dirName);
        sdd.useUnicode = false;
        // format byte + path + null terminator

Das steht im Gegensatz zu den **Entwicklungsphasen**, in denen Sie ständig den Code ändern, kaputt machen, reparieren, den Entwicklungsserver stoppen und neu starten, usw.

## Deployment-Strategien { #deployment-strategies }

Es gibt mehrere Möglichkeiten, dies zu tun, abhängig von Ihrem spezifischen Anwendungsfall und den von Ihnen verwendeten Tools.

Each file is a list of API features, one per line.

go1.txt (and similarly named files) are frozen once a version has been
shipped. Each file adds new lines but does not remove any.

except.txt lists features that may disappear without breaking true
compatibility.

Starting with go1.19.txt, each API feature line must end in "#nnnnn"

For example, each process has different supported JVMs and a different set of services available for dependency injection.
While a lot of Gradle source code runs only in the Gradle daemon, not all of it does so.
When working on some source code it is important to be aware of the runtimes in which it will run, so that you don't break these constraints.

such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it).  Whether that is true depends on what the Library does
and what the program that uses the Library does.

  1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an

        this.subject = subject;
    }

    /**
     * Construct a <code>Kerb5Authenticator</code> object with <code>Subject</code> and
     * potential NTLM fallback (if the server does not support kerberos).
     *
     * @param subject
     *            represents the user who perform Kerberos authentication. Should at least contain a TGT for the user.
     * @param domain

   * the original exception type.
   *
   * <p>This method always throws, and as such should be called as {@code throw closer.rethrow(e);}
   * to ensure the compiler knows that it will throw.
   *
   * @return this method does not return; it always throws
   * @throws IOException when the given throwable is an IOException
   */
  public RuntimeException rethrow(Throwable e) throws IOException {
    checkNotNull(e);
    thrown = e;

            fos.write("ABCDEFGH".getBytes());
        }

        try (TemporaryFileInputStream stream = new TemporaryFileInputStream(tempFile)) {
            // FileInputStream does not support mark/reset
            assertFalse(stream.markSupported());

            assertEquals('A', stream.read());
            assertEquals('B', stream.read());