e727101957
- Make sure we always await the last flush task before calling FlushAsync again instead of preemptively calling FlushAsync and checking to see if the ValueTask is incomplete before bothering to acquire the _flushLock - This now acquires the _flushLock fore every call to Response.Body.Write whereas this only happened for truly async writes before. - I don't think this is a big concern since this should normally be uncontested, and DefaultPipeWriter.FlushAsync/GetResult already acquire a lock. |
||
|---|---|---|
| .. | ||
| Buffers.MemoryPool | ||
| Buffers.Testing | ||
| CertificateGeneration | ||
| ChunkingCookieManager | ||
| ClosedGenericMatcher | ||
| CopyOnWriteDictionary | ||
| Diagnostics | ||
| E2ETesting | ||
| ErrorPage | ||
| EventSource.Testing | ||
| HttpSys | ||
| ObjectMethodExecutor | ||
| Process | ||
| PropertyActivator | ||
| PropertyHelper | ||
| RangeHelper | ||
| Razor | ||
| RazorViews | ||
| SecurityHelper | ||
| StackTrace | ||
| SyncPoint | ||
| UrlDecoder | ||
| ValueTaskExtensions | ||
| WebEncoders | ||
| test | ||
| NullScope.cs | ||