From 40cc2107cc65cf30cef835a03c520ab1352c472a Mon Sep 17 00:00:00 2001 From: David Renshaw Date: Tue, 17 Sep 2024 13:06:40 -0400 Subject: [PATCH] fix blog misspellings --- blog/_posts/2024-09-17-0.20-release.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/blog/_posts/2024-09-17-0.20-release.md b/blog/_posts/2024-09-17-0.20-release.md index 1b385dd50..1c2f375fd 100644 --- a/blog/_posts/2024-09-17-0.20-release.md +++ b/blog/_posts/2024-09-17-0.20-release.md @@ -96,7 +96,7 @@ async fn write_bytes_chunked( Now the bytes should transfer much more smoothly, but we've introduced a new problem: latency. -After sending each `ByteStream.write()` request, +After sending each `ByteSink.write()` request, we're waiting for the server to send back its response before we start the next request. That will likely slow things down considerably! @@ -210,11 +210,11 @@ any code change from users. ## implementing streaming methods -To create an instance of a `ByteSinkStreaming` object in Rust, +To create an instance of a `StreamingByteSink` object in Rust, we need to implement the `byte_sink_streaming::Server` trait: ```rust -impl byte_sink_streaming::Server for ByteStreamImpl { +impl byte_sink_streaming::Server for StreamingByteSinkImpl { fn write( &mut self, params: byte_sink_streaming::WriteParams