Closed Tratcher closed 9 years ago
Hi @Tratcher, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution! You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;
Just some fairly small comments, the code overall looks good. I like the new unit tests.
Open question: Should there be a (configurable) limit on how much data to buffer before disabling buffering and flushing?
Updated
Looks :shipit: to me.
:shipit:
@davidfowl @lodejard waiting on an explicit sign-off to confirm the design concepts.
Updated with Louis's feedback about preventing random access to the buffer. Added a sample.
@lodejard
https://github.com/aspnet/Hosting/issues/299
This PR seeks to formalize the discussion from https://github.com/aspnet/HttpAbstractions/wiki/Rolling-Notes about how response buffering components should behave. In this case we've implemented a fully buffered response. Buffering is disabled via a feature interface or by calling Flush.
The one notable departure from the notes is that we use Stream.SetLength to truncate/reset the buffer, where Position is just used to move around your write marker.
@davidfowl @lodejard @Eilon