{* ../../docs_src/events/tutorial003_py310.py hl[22] *}

## Alternative Events (<abbr title="veraltet, obsolet: Es soll nicht mehr verwendet werden">deprecatet</abbr>) { #alternative-events-deprecated }

/// warning | Achtung

![Swagger UI](https://fastapi.tiangolo.com/img/index/index-01-swagger-ui-simple.png)

### Alternative API-Dokumentation { #alternative-api-docs }

Und jetzt gehen Sie auf [http://127.0.0.1:8000/redoc](http://127.0.0.1:8000/redoc).

Sie sehen die alternative automatische Dokumentation (bereitgestellt von [ReDoc](https://github.com/Rebilly/ReDoc)):

        failover.handleFailure(failedChannel, error);

        // Verify pending operations were cleared from failed channel
        assertEquals(0, failedChannel.getRequestsPending());

        // Verify alternative channel was selected and operation added
        verify(mockLoadBalancer).selectChannel(mockOperation);
        verify(alternativeChannel).addPendingOperation(mockOperation);
    }

    @Test

///

## Nützliche Standards, alternative Dokumentation { #standards-based-benefits-alternative-documentation }

Und weil das generierte Schema vom [OpenAPI](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.1.0.md)-Standard kommt, gibt es viele kompatible Tools.

        .build()
    server.useHttps(serverHandshakeCertificates.sslSocketFactory())
    url = server.url("/robots.txt")
  }

  /**
   * Test connecting to the main host then an alternative, although only subject alternative names
   * are used if present no special consideration of common name.
   */
  @Test
  fun commonThenAlternative() {
    server.enqueue(MockResponse())
    server.enqueue(MockResponse())

> 這個專案的歷史是什麼？看起來它在短短幾週內從默默無名變得非常厲害 [...]

以下是其中一小段歷史。

## 替代方案 { #alternatives }

多年來我一直在打造具有複雜需求的 API（機器學習、分散式系統、非同步工作、NoSQL 資料庫等），並帶領多個開發團隊。

在此過程中，我需要調查、測試並使用許多替代方案。

**FastAPI** 的歷史，在很大程度上也是其前身工具的歷史。

如在[替代方案](alternatives.md)一節所述：

<blockquote markdown="1">

若沒有他人的前期成果，就不會有 **FastAPI**。

先前已有許多工具啟發了它的誕生。

@J2ktIncompatible // Super-sourced
abstract class GwtFluentFutureCatchingSpecialization<V extends @Nullable Object>
    extends AbstractFuture<V> {
  /*
   * This server copy of the class is empty. The corresponding GWT copy contains alternative
   * versions of catching() and catchingAsync() with slightly different signatures from the ones
   * found in FluentFuture.java.
   */

      required: false
  - type: textarea
    id: context
    attributes:
      label: Context
      description: |
        How has this issue affected you? What are you trying to accomplish? What other alternatives have you considered?
        Providing context helps us come up with a solution that is most useful in the real world
    validations:

import org.jspecify.annotations.Nullable;

/**
 * Weak reference with a {@code finalizeReferent()} method which a background thread invokes after
 * the garbage collector reclaims the referent. This is a simpler alternative to using a {@link
 * ReferenceQueue}.
 *
 * @author Bob Lee
 * @since 2.0
 */
@J2ktIncompatible
@GwtIncompatible
public abstract class FinalizableWeakReference<T> extends WeakReference<T>

 * different signatures.
 */
@GwtCompatible
@J2ktIncompatible // Super-sourced
abstract class GwtFuturesCatchingSpecialization {
  /*
   * This server copy of the class is empty. The corresponding GWT copy contains alternative
   * versions of catching() and catchingAsync() with slightly different signatures from the ones
   * found in Futures.java.
   */