Update request-response.md (#35289)

* Update request-response.md

* Apply suggestions from code review

Co-authored-by: Günther Foidl <[email protected]>

* response body

* Update aspnetcore/fundamentals/middleware/request-response.md

* Update aspnetcore/fundamentals/middleware/request-response.md

* Update aspnetcore/fundamentals/middleware/request-response.md

* Update request-response.md

* Update aspnetcore/fundamentals/middleware/request-response.md

* Update aspnetcore/fundamentals/middleware/request-response.md

* Update request-response.md

* Update aspnetcore/fundamentals/middleware/request-response.md

* Update aspnetcore/fundamentals/middleware/request-response.md

* Update aspnetcore/fundamentals/middleware/request-response.md

* Update aspnetcore/fundamentals/middleware/request-response.md

Co-authored-by: Günther Foidl <[email protected]>

* Update aspnetcore/fundamentals/middleware/request-response.md

* Update aspnetcore/fundamentals/middleware/request-response.md

---------

Co-authored-by: Günther Foidl <[email protected]>

Author: Rick-Anderson

aspnetcore/fundamentals/middleware/request-response.md

@@ -5,7 +5,7 @@ description: Learn how to read the request body and write the response body in A
 monikerRange: '>= aspnetcore-3.0'
 ms.author: tdykstra
 ms.custom: mvc
-ms.date: 5/29/2019
+ms.date: 4/22/2025
 uid: fundamentals/middleware/request-response
 ---
 # Request and response operations in ASP.NET Core
@@ -25,7 +25,10 @@ There are two abstractions for the request and response bodies: <xref:System.IO.
 * `TextWriter`
 * `HttpResponse.WriteAsync`
 
-Streams aren't being removed from the framework. Streams continue to be used throughout .NET, and many stream types don't have pipe equivalents, such as `FileStreams` and `ResponseCompression`.
+Streams aren't being removed from the framework. Streams continue to be used throughout .NET:
+
+* Many stream types don't have pipe equivalents, such as `FileStreams` and `ResponseCompression`.
+* It's straightforward adding compression to a stream.
 
 ## Stream examples
 
@@ -70,7 +73,7 @@ These issues are fixable, but the code is becoming progressively more complicate
 
 ## Pipelines
 
-The following example shows how the same scenario can be handled using a [PipeReader](/dotnet/standard/io/pipelines#pipe):
+The following example shows how the preceding stream scenario can be handled using a [PipeReader](/dotnet/standard/io/pipelines#pipe):
 
 [!code-csharp[](request-response/samples/3.x/RequestResponseSample/Startup.cs?name=GetListOfStringFromPipe)]
 
@@ -80,6 +83,13 @@ This example fixes many issues that the streams implementations had:
 * Encoded strings are directly added to the list of returned strings.
 * Other than the `ToArray` call, and the memory used by the string, string creation is allocation free.
 
+When writing directly to `HttpResponse.BodyWriter`, call `PipeWriter.FlushAsync` manually to ensure the data is flushed to the underlying response response body. Here's why:
+
+* `HttpResponse.BodyWriter` is a `PipeWriter` that buffers data until a flush operation is triggered.
+* Calling `FlushAsync` writes the buffered data to the underlying response body.
+
+It's up to the developer to decide when to call `FlushAsync`, balancing factors such as buffer size, network write overhead, and whether the data should be sent in discrete chunks. For more information, see [System.IO.Pipelines in .NET](/dotnet/standard/io/pipelines).
+
 ## Adapters
 
 The `Body`, `BodyReader`, and `BodyWriter` properties are available for `HttpRequest` and `HttpResponse`. When you set `Body` to a different stream, a new set of adapters automatically adapt each type to the other. If you set `HttpRequest.Body` to a new stream, `HttpRequest.BodyReader` is automatically set to a new `PipeReader` that wraps `HttpRequest.Body`.