r, err := h.Call(ctx, c.connection, args)
	if err != nil {
		return false, err
	}
	defer h.PutResponse(r)
	ok = r.Code == dsync.RespOK
	switch r.Code {
	case dsync.RespLockConflict, dsync.RespLockNotFound, dsync.RespOK:
	// no error
	case dsync.RespLockNotInitialized:
		err = errLockNotInitialized
	default:
		err = errors.New(r.Err)
	}
	return ok, err
}

> Requests est l'un des packages Python les plus téléchargés de tous les temps

La façon dont vous l'utilisez est très simple. Par exemple, pour faire une requête `GET`, vous devez écrire :

```Python
response = requests.get("http://example.com/some/url")
```

L’opération de chemin d'accès correspondante dans **FastAPI** pourrait ressembler à ceci :

```Python hl_lines="1"
@app.get("/some/url")
def read_url():

     * @return The SuggestDeleteResponse.
     */
    public SuggestDeleteResponse deleteAll() {
        ensureOperations();
        final SuggestDeleteResponse response = deletionOps.deleteAll(index);
        restoreElevateWord();
        return response;
    }

    /**
     * Deletes document words.
     * @return The SuggestDeleteResponse.
     */
    public SuggestDeleteResponse deleteDocumentWords() {

import okhttp3.Headers

/** An HTTP request initiated by the server. */
public class PushPromise(
  public val method: String,
  public val path: String,
  public val headers: Headers,
  public val response: MockResponse,

    context.close()
    browser.close()


process = subprocess.Popen(
    ["fastapi", "run", "docs_src/json_base64_bytes/tutorial001_py310.py"]
)
try:
    for _ in range(3):
        try:
            response = httpx.get("http://localhost:8000/docs")
        except httpx.ConnectError:
            time.sleep(1)
            break
    with sync_playwright() as playwright:
        run(playwright)
finally:

HTTP/1 [Response.Body] now automatically drains any unread content upon being
closed, up to a conservative limit, to allow better connection reuse. For most
programs, this change should be a no-op, or result in a performance improvement.
In rare cases, programs that do not benefit from connection reuse might
experience performance degradation if they had been improperly allowing an
excessive amount of idle connections to linger; usually by setting

        }

        @Test
        @DisplayName("Should be usable as both request and response")
        void testDualInterfaceUsage() {
            EncryptionNegotiateContext context = new EncryptionNegotiateContext();

            NegotiateContextRequest request = context;
            NegotiateContextResponse response = context;

Let's start with a simple FastAPI application:

{* ../../docs_src/generate_clients/tutorial001_py310.py hl[7:9,12:13,16:17,21] *}

Notice that the *path operations* define the models they use for request payload and response payload, using the models `Item` and `ResponseMessage`.

### API Docs { #api-docs }

If you go to `/docs`, you will see that it has the **schemas** for the data to be sent in requests and received in responses:

import org.lastaflute.web.api.ApiFailureHook;
import org.lastaflute.web.api.ApiFailureResource;
import org.lastaflute.web.login.exception.LoginUnauthorizedException;
import org.lastaflute.web.response.ApiResponse;
import org.lastaflute.web.response.JsonResponse;

/**
 * The hook for API failure.
 *
 * @author jflute
 */
public class FessApiFailureHook implements ApiFailureHook { // #change_it for handling API failure

     * If an error occurs during execution, it will be cached and re-thrown for subsequent identical requests.
     *
     * @param <REQ> The request type
     * @param <REP> The response type
     * @param req The request object used as the cache key
     * @param supplier The function to execute and cache the result
     * @return The result from the supplier (either fresh or cached)