look at the output caching story as MS have some stuff Ocelot could just use

ThreeMammals / Ocelot

.NET API Gateway

https://www.nuget.org/packages/Ocelot

MIT License

8.31k stars 1.63k forks source link

look at the output caching story as MS have some stuff Ocelot could just use #1196

Open TomPallister opened 4 years ago

TomPallister commented 4 years ago

Expected Behavior / New Feature

Response caching in ASP.NET Core

raman-m commented 5 months ago

Yes, I agree! We have the separate Caching package aka Ocelot.Cache.CacheManager. How did we get to this point by ignoring native ASP.NET implementations? I believe ASP.NET Core team had implemented Caching since ages of ASP.NET Core 1.1 in 2016... :question: So, we value third party packages but ignore ASP.NET packages. This is a strange situation.

raman-m commented 5 months ago

@ggnaegi @RaynaldM FYI

RaynaldM commented 5 months ago

Response caching is a special form of caching, since it can be instructed (in the headers) to store the cache on the client and/or server side. I'm not sure it's very useful for a gateway (and even a bit difficult to debug in case of a problem), it's normally intended for "real" WEB applications (of the "Razor" type).

raman-m commented 5 months ago

Anyway, in my opinion OutputCache feature and middleware require some design review. But it has low priority...