# Page Not Found

The URL `overview-the-websocket-mechanism` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Overview The WebSocket Mechanism](https://xiang753017.gitbook.io/zixiang-blog/http/overview-the-websocket-mechanism.md)
- [How do AppRTC work in WebRTC mechanism ?](https://xiang753017.gitbook.io/zixiang-blog/how-do-apprtc-work-in-webrtc-mechanism.md)
- [[系統設計]- 容易產生設計盲點](https://xiang753017.gitbook.io/zixiang-blog/xi-tong-she-ji-rong-yi-chan-sheng-she-ji-mang-dian.md)
- [Microservice Pattern 犧牲了什麼？](https://xiang753017.gitbook.io/zixiang-blog/patterns/microservice-pattern-xi-sheng-le-shen-mo.md)
- [How do pick the database more correctly?](https://xiang753017.gitbook.io/zixiang-blog/database/how-do-pick-the-database-more-correctly.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://xiang753017.gitbook.io/zixiang-blog/http/overview-the-websocket-mechanism.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://xiang753017.gitbook.io/zixiang-blog/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://xiang753017.gitbook.io/zixiang-blog/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/zixiang-blog/http/overview-the-websocket-mechanism.md`).

You may also use `Accept: text/markdown` header for content negotiation.