Skip to content

Update Working-with-Cap'n-Proto-Types.md #302

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.

Sign up for GitHub

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

Merged
zenhack merged 1 commit into from
Sep 10, 2022
Merged

Update Working-with-Cap'n-Proto-Types.md #302

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/Working-with-Cap'n-Proto-Types.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,7 +130,7 @@ Cap'n Proto supports a [packed encoding](https://capnproto.org/encoding.html#pac

## Streaming

The `Marshal` and `MarshalPacked` methods are suitable for such things as writing capnp types to a file, or sending a single objet over the network, e.g. in an HTTP request. But if you want to stream multiple objects over, say, a network connection, you'll need a way of "framing" the stream, _i.e._ of separating the byte stream into different objects. For this, we use the `Encoder` and `Decoder` types.
The `Marshal` and `MarshalPacked` methods are suitable for such things as writing capnp types to a file, or sending a single object over the network, e.g. in an HTTP request. But if you want to stream multiple objects over, say, a network connection, you'll need a way of "framing" the stream, _i.e._ of separating the byte stream into different objects. For this, we use the `Encoder` and `Decoder` types.

The `Encoder` and `Decoder` types allow you to stream generated types to and from any `io.Writer` or `io.Reader`, respectively.

Expand Down