執行順序大致如下圖。時間從上往下流動，每一欄代表一個互動或執行程式碼的部分。

```mermaid
sequenceDiagram

participant client as Client
participant handler as Exception handler
participant dep as Dep with yield
participant operation as Path Operation
participant tasks as Background tasks

    Note over client,operation: Can raise exceptions, including HTTPException
    client ->> dep: Start request
    Note over dep: Run code up to yield
    opt raise Exception

        byte[] server = hex("0102030405060708");
        byte[] client = hex("FEEDFACECAFEBEEF");

        // Act
        byte[] expected = NtlmUtil.computeResponse(key, server, client, 0, client.length);
        byte[] actual = NtlmUtil.getLMv2Response(key, server, client);

        // Assert
        assertArrayEquals(expected, actual);
    }

    @Test

  var client = clientTestRule.newClient()

  @StartStop
  private val server = MockWebServer()

  @BeforeEach
  fun setUp() {
    platform.assumeOpenJSSE()
  }

  @Test
  fun testTlsv13Works() {
    enableTls()

    server.enqueue(MockResponse(body = "abc"))

    val request = Request(server.url("/"))

    val response = client.newCall(request).execute()

    /**
     * Gets the appropriate crawler client for the given URL.
     * @param url The URL to get a client for.
     * @return The crawler client.
     */
    protected CrawlerClient getClient(final String url) {
        return clientFactory.getClient(url);
    }

    /**
     * Checks if the content has been updated since the last crawl.
     * @param client The crawler client.
     * @param urlQueue The URL queue entry.

	if m.closed {
		return errors.New("mux client closed")
	}
	return m.sendLocked(msg)
}

// sendLocked the message. msg.Seq and msg.MuxID will be set.
// m.respMu must be held.
func (m *muxClient) sendLocked(msg message) error {
	dst := GetByteBufferCap(msg.Msgsize())
	msg.Seq = m.SendSeq
	msg.MuxID = m.MuxID
	msg.Flags |= m.BaseFlags
	if debugPrint {
		fmt.Println("Client sending", &msg, "to", m.parent.Remote)
	}

<img src="/img/tutorial/generate-clients/image02.png">

보낼 페이로드에 대해서도 자동 완성이 제공됩니다:

<img src="/img/tutorial/generate-clients/image03.png">

/// tip | 팁

`name`과 `price`에 대한 자동 완성은 FastAPI 애플리케이션에서 `Item` 모델에 정의된 내용입니다.

///

전송하는 데이터에 대해 인라인 오류도 표시됩니다:

<img src="/img/tutorial/generate-clients/image04.png">

응답 객체도 자동 완성을 제공합니다:

<img src="/img/tutorial/generate-clients/image05.png">

                            "400": {"description": "Client error level 0"},
                            "401": {"description": "Client error level 1"},
                            "402": {"description": "Client error level 2"},
                            "403": {"description": "Client error level 3"},
                            "404": {"description": "Client error level 4"},

```mermaid
sequenceDiagram

participant client as Client
participant handler as Exception handler
participant dep as Dep with yield
participant operation as Path Operation
participant tasks as Background tasks

    Note over client,operation: Can raise exceptions, including HTTPException
    client ->> dep: Start request
    Note over dep: Run code up to yield
    opt raise Exception

* The [Gradle Tooling API client](https://docs.gradle.org/8.8/userguide/third_party_integration.html#embedding)
  * This requires a Java application, and thus runtime, to run the tooling API client

As indicated, each of those components require a Java runtime to run.

The recommended way of invoking Gradle is to use the Gradle Wrapper.

		<postConstruct name="init"/>
	</component>

	<!-- LLM client manager -->
	<component name="llmClientManager" class="org.codelibs.fess.llm.LlmClientManager">
	</component>

	<!-- LLM client components are provided by fess-llm-* plugins via fess_llm++.xml -->