```

#### 1.2 Implementation Tasks
- [ ] Define lease state constants (SMB2_LEASE_READ, SMB2_LEASE_HANDLE, SMB2_LEASE_WRITE)
- [ ] Implement lease key generation and management
- [ ] Add lease context to Create request/response
- [ ] Implement lease break notification handling
- [ ] Modify SmbFile to support lease-based caching
- [ ] Add lease upgrade/downgrade logic
- [ ] Implement lease epoch tracking for v2 leases

{* ../../docs_src/header_params/tutorial003_an_py310.py hl[9] *}

If you communicate with that *path operation* sending two HTTP headers like:

```
X-Token: foo
X-Token: bar
```

The response would be like:

```JSON
{
    "X-Token values": [
        "bar",
        "foo"
    ]
}
```

## Recap { #recap }

<img src="/img/deployment/https/https05.drawio.svg">

### HTTP-відповідь { #http-response }

Застосунок обробить запит і надішле **звичайну (незашифровану) HTTP-відповідь** TLS Termination Proxy.

<img src="/img/deployment/https/https06.drawio.svg">

### HTTPS-відповідь { #https-response }

如果你的应用需要接收和发送 JSON 数据，但其中需要包含二进制数据，可以将其编码为 base64。

## Base64 与文件 { #base64-vs-files }

请先考虑是否可以使用 [请求文件](../tutorial/request-files.md) 来上传二进制数据，并使用 [自定义响应 - FileResponse](./custom-response.md#fileresponse--fileresponse-) 来发送二进制数据，而不是把它编码进 JSON。

JSON 只能包含 UTF-8 编码的字符串，因此无法直接包含原始字节。

Base64 可以把二进制数据编码为字符串，但为此会使用比原始二进制更多的字符，因此通常比直接使用文件的效率更低。

仅当你确实需要在 JSON 中包含二进制数据且无法使用文件时，才使用 base64。

/**
 * SMB1 transaction subcommand for transacting with a named pipe.
 *
 * This class implements the TRANS_TRANSACT_NAMED_PIPE transaction which
 * combines writing data to a pipe and reading the response in a single operation.
 * This is more efficient than separate write and read operations.
 */
public class TransTransactNamedPipe extends SmbComTransaction {

{* ../../docs_src/header_params/tutorial003_an_py310.py hl[9] *}

Si te comunicas con esa *path operation* enviando dos headers HTTP como:

```
X-Token: foo
X-Token: bar
```

El response sería como:

```JSON
{
    "X-Token values": [
        "bar",
        "foo"
    ]
}
```

## Recapitulación { #recap }

 */
package okhttp3.internal.ws

import okio.Buffer
import okio.ByteString.Companion.encodeUtf8

object WebSocketProtocol {
  /** Magic value which must be appended to the key in a response header. */
  internal const val ACCEPT_MAGIC = "258EAFA5-E914-47DA-95CA-C5AB0DC85B11"

  /*
  Each frame starts with two bytes of data.

   0 1 2 3 4 5 6 7    0 1 2 3 4 5 6 7
  +-+-+-+-+-------+  +-+-------------+

По‑прежнему можно использовать один `BackgroundTask` в FastAPI, но тогда вам нужно создать объект в своём коде и вернуть Starlette `Response`, включающий его.

Подробнее см. в [официальной документации Starlette по фоновым задачам](https://www.starlette.dev/background/).

## Предостережение { #caveat }

注意，測試函式現在是 `async def`，而不是像使用 `TestClient` 時那樣僅用 `def`。

///

接著，我們可以用該應用建立 `AsyncClient`，並以 `await` 發送非同步請求。

{* ../../docs_src/async_tests/app_a_py310/test_main.py hl[9:12] *}

這等同於：

```Python
response = client.get('/')
```

也就是先前用 `TestClient` 發送請求時所用的寫法。

/// tip

注意，對新的 `AsyncClient` 需搭配 async/await —— 請求是非同步的。

///

/// warning

///

Ardından app ile bir `AsyncClient` oluşturup `await` kullanarak ona async request'ler gönderebiliriz.

{* ../../docs_src/async_tests/app_a_py310/test_main.py hl[9:12] *}

Bu, şu kullanıma denktir:

```Python
response = client.get('/')
```

...ki daha önce request'leri `TestClient` ile bu şekilde gönderiyorduk.

/// tip | İpucu

Yeni `AsyncClient` ile async/await kullandığımızı unutmayın; request asenkron çalışır.

///