Why use a httprequeststreamreader instead of streamreader

Question

0.00/5 (No votes)

See more:

We're working on a Web API and need to read (part of) the stream in middleware for logging purposes. I came across the HttpRequestStreamReader[^] at some point, however, I can't find why this would be preferred over a regular StreamReader. Does anyone know?

What I have tried:

Reading the documentation, searching the web

Posted 31-May-22 4:40am

Maarten Kools

Add a Solution

Comments

[no name] 1-Jun-22 1:42am

It may just be a namespace packaging convenience ("web utilities"). And the http version doesn't have a "block read".

Member 15627495 1-Jun-22 3:48am

Http is at network/server level,

streamreader prefers hard-drives/memory

sure it's a special class for Http. dedicated to http. a highway for the use.

Maarten Kools 1-Jun-22 4:08am

But is there a real difference in implementation? Because I skimmed through the code, and the only obvious difference I can see is that the HttpRequestStreamReader rents a buffer from the pool, while the StreamReader just creates a new buffer. So I assume this alleviates memory pressure. Aside from that, it reads a stream, and doesn't seem to care where the stream comes from.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Member 15627495 · Answer 1 · 2022-05-31T22:40:00

You're coding in .Net environment :

The Memory is often managed and auto-clean ( finalize function in class / dispose for lots of components / and GC as big helper ).

As I told you, you evolve in 'network buffer' for request / web server.

The HttpRequestStreamReader and streamreader are both stream, sure.
a streamreader can handle the http one.

but for simple use, the dedicated class HttpRequestStreamReader offers you dedicated features in its class.
that the point,

it's not for "handle level" in .Net, it's for "facilities and uses, and features".

StreamReader is from "system.IO"
HttpRequestStreamReader is part of ASP namespace, but a TextStream ( reader )
HttpRequestStreamReader Class (Microsoft.AspNetCore.WebUtilities) | Microsoft Docs[^]