This gives you a lot of **flexibility**. You can return any data type, override any data declaration or validation, etc.

It also gives you a lot of **responsibility**. You have to make sure that the data you return is correct, in the correct format, that it can be serialized, etc.

## Using the `jsonable_encoder` in a `Response` { #using-the-jsonable-encoder-in-a-response }

        client.setInitParameterMap(params);
    }

    /**
     * Executes the request with retry logic.
     * @param request The request data.
     * @return The response data.
     */
    @Override
    public ResponseData execute(final RequestData request) {
        if (listener != null) {
            listener.onRequestStart(this, request);
        }

func TestScanner(t *testing.T) {
	t.Skip("Unstable test")
	data := []byte("abcdefghijklmnopqrstuvwxyz0123456789")

	var i int
	r := bytes.NewReader(data)
	scanner := newScanner(r)
	for scanner.pos < atomic.LoadInt64(&scanner.end) {
		c := scanner.next()
		if scanner.readerErr != nil {
			t.Fatal(scanner.readerErr)
		}
		if c != data[i] {
			t.Fatalf("expected %s, got %s", string(data[i]), string(c))
		}

    }

    /**
     * Deserializes data from access result data.
     *
     * @param accessResultData the access result data containing serialized data
     * @return the deserialized object
     */
    @Override
    public Object getData(final AccessResultData<?> accessResultData) {
        final byte[] data = accessResultData.getData();
        if (data != null) {
            try {

        // Create a mock DfsReferralData object
        DfsReferralData mockData = mock(DfsReferralData.class);

        // Create a DfsReferral instance with the mock data
        DfsReferral dfsReferral = new DfsReferral(mockData);

        // Verify that getData() returns the same mock data object
        assertEquals(mockData, dfsReferral.getData(), "getData() should return the DfsReferralData object passed to the constructor.");
    }

    /**

		<i class="fa fa-pencil-alt" aria-hidden="true"></i>
		<la:message key="labels.crud_button_edit" />
	</button>
	<button type="button" class="btn btn-danger" name="delete"
		data-toggle="modal" data-target="#confirmToDelete"
		value="<la:message key="labels.crud_button_delete" />">
		<i class="fa fa-trash" aria-hidden="true"></i>
		<la:message key="labels.crud_button_delete" />
	</button>

SSE 是一種透過 HTTP 從伺服器向用戶端串流傳送資料的標準。

每個事件都是一個小型文字區塊，包含 `data`、`event`、`id` 和 `retry` 等「欄位」，並以空白行分隔。

看起來像這樣：

```
data: {"name": "Portal Gun", "price": 999.99}

data: {"name": "Plumbus", "price": 32.99}

```

SSE 常用於 AI 聊天串流、即時通知、日誌與可觀察性，以及其他由伺服器主動推送更新給用戶端的情境。

/// tip

如果你要串流二進位資料，例如影片或音訊，請參考進階指南：[串流資料](../advanced/stream-data.md)。

///

## 使用 FastAPI 串流 SSE { #stream-sse-with-fastapi }

            logger.debug("Displaying chat page. chatEnabled=true");
        }

        return asHtml(virtualHost(path_Chat_ChatJsp)).useForm(SearchForm.class).renderWith(data -> {
            RenderDataUtil.register(data, "chatEnabled", true);
            RenderDataUtil.register(data, "chatPage", true);
            // Label type items for filter UI

    category=FastAPIDeprecationWarning,
    stacklevel=2,
)
class UJSONResponse(JSONResponse):
    """JSON response using the ujson library to serialize data to JSON.

    **Deprecated**: `UJSONResponse` is deprecated. FastAPI now serializes data
    directly to JSON bytes via Pydantic when a return type or response model is
    set, which is faster and doesn't need a custom response class.

    Read more in the

        // DFS path offset (2 bytes) - points to string data
        SMBUtil.writeInt2(stringDataStart - 8, buffer, 20); // Offset from start of referral

        // DFS alternate path offset (2 bytes)
        SMBUtil.writeInt2(0, buffer, 22);

        // Network address offset (2 bytes)
        SMBUtil.writeInt2(0, buffer, 24);

        // Padding to align string data
        buffer[26] = 0;
        buffer[27] = 0;