-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transalte current CloudHub docs to Chinese. #599
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Welcome @bettermultiply! It looks like this is your first PR to kubeedge/website 🎉 |
Hello, I am learning about using KubeEdge, so I think translate its documentation is the best way to do that. But I have some question when translating this page.
|
e9b58e1
to
454f4a2
Compare
Signed-off-by: BetMul <[email protected]>
channelQ is a concept from the early versions. I checked the commit history and confirmed that it was replaced by dispatcher during the cloudhub refactoring in release-1.12. |
|
||
CloudHub is one module of cloudcore and is the mediator between Controllers and the Edge side. It supports both web-socket based connection as well as a [QUIC](https://quicwg.org/ops-drafts/draft-ietf-quic-applicability.html) protocol access at the same time. | ||
The edgehub can choose one of the protocols to access to the cloudhub. CloudHub's function is to enable the communication between edge and the Controllers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the content of CloudHub's function is to enable the communication between edge and the Controllers
is missing
- 获取消息上下文并为事件创建 ChannelQ | ||
- 通过 WebSocket 创建 HTTP 连接 | ||
- 保持 WebSocket 连接 | ||
- 从读取边缘信息 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
从读取边缘信息
-> 从边缘端读取信息
- 通过 WebSocket 创建 HTTP 连接 | ||
- 保持 WebSocket 连接 | ||
- 从读取边缘信息 | ||
- 向边缘写入信息 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i perfer to 边缘侧
|
||
### Read message from edge: | ||
### 从读取边缘信息: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
从读取边缘信息
->从边缘端读取信息
Which issue(s) this PR fixes:
Fixes #584
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
I update the current CloudHub docs.
What is the current behavior? (You can also link to an open issue here)
English in Chinese version
What is the new behavior (if this is a feature change)?
Chinese in Chinese version
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
Other information: