* Add AOT /1
* Add AOT /1
* Add AOT /1
* Add AOT /1
* Update aspnetcore/fundamentals/openapi/samples/9.x/GetDocument.Insider/Program.cs
Co-authored-by: Mike Kistler <mikekistler@microsoft.com>
* Add AOT /1
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
---------
Co-authored-by: Mike Kistler <mikekistler@microsoft.com>
* Add important notes on HybridCache limitations and behavior
- Added a note indicating that removing cache entries by tag is still under development and is currently non-functional.
- Clarified that cache invalidation by key or tags affects only the current node and secondary storage, but not other nodes' in-memory cache.
* Update references for API Testing
* Update aspnetcore/fundamentals/minimal-apis/bindingArrays/7.0-samples/todo/Program.cs
Co-authored-by: Tom Dykstra <tdykstra@microsoft.com>
---------
Co-authored-by: Tom Dykstra <tdykstra@microsoft.com>
* Document CompressionLevel.SmallestSize and actual Gzip/Brotli compression levels
Since [.Net 6](7d527c3368) there has been an additional option: `CompressionLevel.SmallestSize`. And since .Net 7 `Optimal` was [fixed](f281393412) to not mean smallest size anymore but rather a balanced value.
This change is also documents what these abstracted `CompressionLevel` values means for Gzip and Brotli compression libraries, given those are enabled by default. In my case I came to this page wanting to get an Idea of balancing CPU use vs size of the response, as there are plenty of pages online benchmarking zlib vs brotli at all possible levels and cpu types.
* Update aspnetcore/performance/response-compression.md
* Update aspnetcore/performance/response-compression.md
Co-authored-by: Tom Dykstra <tdykstra@microsoft.com>
* Update aspnetcore/performance/response-compression.md
---------
Co-authored-by: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
Co-authored-by: Tom Dykstra <tdykstra@microsoft.com>