move blog post from _drafts to _posts

capnproto · Sep 17, 2024 · 7000a0a · 7000a0a
1 parent 1722f1b
commit 7000a0a
Showing 1 changed file with 4 additions and 3 deletions.
diff --git a/blog/_drafts/0.20-release.md → blog/_posts/2024-09-17-0.20-release.md b/blog/_drafts/0.20-release.md → blog/_posts/2024-09-17-0.20-release.md
@@ -30,7 +30,7 @@ In Rust code, we can invoke methods on a (possibly-remote) `ByteSink` object
 through handles of type `byte_sink::Client`. For example:
 
 ```rust
-/// Writes all of `bytes` to `sink` in a call to `write()`.
+/// Writes all of `bytes` to `sink` in a single call to `write()`.
 async fn write_bytes_all_at_once(
     bytes: &[u8],
     sink: byte_sink::Client,
@@ -202,7 +202,8 @@ async fn write_bytes_streaming(
 Behind the scenes, capnproto-rust maintains a limit on how many bytes
 are in flight for this object at any given time.
 Currently it uses a fixed value
-that can be configured via `twoparty::VatNetwork::set_window_size()`.
+that can be configured via
+[`twoparty::VatNetwork::set_window_size()`](https://github.com/capnproto/capnproto-rust/blob/1722f1baadd56f7f34d1dc2ee2ee1d5da12838db/capnp-rpc/src/twoparty.rs#L282-L284).
 In the future, the library could potentially add sophisticated dynamic
 flow control to optimize throughput, without requiring
 any code change from users.
@@ -252,5 +253,5 @@ in capnproto-rust.
 ## example
 
 For a working example, see
-the [capnp-rpc/examples/streaming](https://github.com/capnproto/capnproto-rust/tree/master/capnp-rpc/examples/streaming)
+the [capnp-rpc/examples/streaming](https://github.com/capnproto/capnproto-rust/tree/1722f1baadd56f7f34d1dc2ee2ee1d5da12838db/capnp-rpc/examples/streaming)
 directory.