Skip to content

Commit b676597

Browse files
authored
docs: Update Kitex+StreamX+-+Stream+Metainfo.md (#1396)
1 parent 5c7e005 commit b676597

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

content/en/docs/kitex/Tutorials/basic-feature/streamx/Kitex+StreamX+-+Stream+Metainfo.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -73,10 +73,10 @@ tl, err := stream.Trailer()
7373

7474
## FAQ
7575

76-
### Why is the reverse pass-through interface inconsistent with 's reverse pass-through?
76+
### Why is the reverse pass-through interface inconsistent with PingPong's reverse pass-through?
7777

78-
Because the concept of flow is different from , under the flow, the Header can be sent independently, which means that my server can send the Header in the first second, send the Data after 10 seconds, and send the Trailer after 1 second.
78+
Because the concept of flow is different from PingPong. On top of streams, the Header can be sent independently, which means that my server can send the Header in the first second, send the Data after 10 seconds, and send the Trailer after 1 second.
7979

80-
At the same time, the client can also choose whether to call `.Header()` or `.Trailer ()` to block.
80+
At the same time, the client can also choose whether to call `.Header()` or `.Trailer ()` to block and wait for the meta info.
8181

8282
Therefore, the semantics of traditional ctx cannot meet the reverse pass-through function of streams. Forward pass-through is still consistent with the original.

0 commit comments

Comments
 (0)