verify(transportPool).getChallenge(context, address);
            verify(transportPool).logon(context, address);
        }

        @Test
        @DisplayName("Should manage multiple transport types")
        void testMultipleTransportTypes() throws Exception {
            // Given
            SmbTransport sharedTransport = mock(SmbTransport.class);

# 額外的模型 { #extra-models }

延續前一個範例，通常會有不只一個彼此相關的模型。

對使用者模型尤其如此，因為：

* 「輸入模型」需要能包含密碼。
* 「輸出模型」不應包含密碼。
* 「資料庫模型」通常需要儲存雜湊後的密碼。

/// danger

切勿儲存使用者的明文密碼。務必只儲存可供驗證的「安全雜湊」。

若你還不清楚，稍後會在[安全性章節](security/simple-oauth2.md#password-hashing)學到什麼是「密碼雜湊」。

///

## 多個模型 { #multiple-models }

以下是模型大致長相、與其密碼欄位以及它們被使用的位置：

{* ../../docs_src/extra_models/tutorial001_py310.py hl[7,9,14,20,22,27:28,31:33,38:39] *}

///

/// note | Technische Details
Etwas Text
///

/// check | Testen
Etwas Text
///

/// tip | Tipp
Etwas Text
///

/// warning | Achtung
Etwas Text
///

/// danger | Gefahr
Etwas Text
///

////

//// tab | Info

Tabs und `Info`/`Note`/`Warning`/usw. Blöcke sollten die Übersetzung ihres Titels nach einem vertikalen Strich (`|`) erhalten.

 * and data sources based on the configured crawling settings.
 *
 * <p>The job supports selective crawling by specifying configuration IDs for different
 * types of crawlers (web, file, data). It manages the crawler process lifecycle,
 * handles timeout scenarios, and ensures proper cleanup of resources.</p>
 *
 * <p>Key features:</p>
 * <ul>
 *   <li>Concurrent crawler process management with configurable limits</li>

 * managing document lifecycle operations (create, update, delete), and handling
 * thumbnail processing during indexing.
 *
 * <p>The IndexingHelper manages bulk operations, handles retries on failures,
 * and provides various query-based operations for document management.
 * It also integrates with the thumbnail generation system and handles

								<li class="nav-item" data-bs-toggle="tooltip" data-placement="left" title="<la:message key="labels.eol_error" />">
									<a class="nav-link active" href="${eolLink}" target="_olh"><i class="fas fa-times-circle text-danger" aria-hidden="true"></i></a>
								</li>
							</c:if>
							<c:if test="${developmentMode}">
								<li class="nav-item" data-bs-toggle="tooltip" data-placement="left"

import com.orangesignal.csv.CsvConfig;
import com.orangesignal.csv.CsvReader;
import com.orangesignal.csv.CsvWriter;

import jakarta.annotation.Resource;

/**
 * Service class that manages crawling information and parameters.
 * This service provides CRUD operations for crawling sessions and their associated parameters,
 * including session management, cleanup operations, and CSV import/export functionality.
 */

# カスタム Request と APIRoute クラス { #custom-request-and-apiroute-class }

場合によっては、`Request` や `APIRoute` クラスで使われるロジックを上書きしたいことがあります。

特に、ミドルウェアでのロジックの代替として有効な場合があります。

たとえば、アプリケーションで処理される前にリクエストボディを読み取ったり操作したりしたい場合です。

/// danger | 警告

これは「上級」機能です。

FastAPI を始めたばかりの場合は、このセクションは読み飛ばしてもよいでしょう。

///

## ユースケース { #use-cases }

ユースケースの例:

* JSON ではないリクエストボディを JSON に変換する（例: [`msgpack`](https://msgpack.org/index.html)）。

- SSE-C is hardly adopted by most widely used applications, applications prefer server to manage the keys via SSE-KMS or SSE-S3.
- MinIO recommends applications to use SSE-KMS, SSE-S3 for simpler, safer and robust encryption mechanism for replicated buckets.

## Explore Further

    return (timeoutNanos <= 0L) ? 0L : timeoutNanos - (System.nanoTime() - startTime);
  }

  /**
   * Signals some other thread waiting on a satisfied guard, if one exists.
   *
   * <p>We manage calls to this method carefully, to signal only when necessary, but never losing a
   * signal, which is the classic problem of this kind of concurrency construct. We must signal if