-
Notifications
You must be signed in to change notification settings - Fork 8
Frequently Asked Questions
Q: Why are there no implementations of common cache stores included in Cashew?
A: The focus of Cashew is on the HTTP part of caching and not on how stuff is stored. We don't want to create half-arsed implementations for all the common cache stores when there are thousands of others that have done it better than we can hope to do. We're also not interested in maintaining a bunch of different cache implementations since we want to focus on improving the core functionality of Cashew.
Q: Why not just use WinINET caching with the WebRequestHandler?
A: Using WebRequestHandler is not bad in all scenarios, it might be preferable to use when testing if your app needs any form of caching at all. It's worth noting though that there are lots of downsides to using it in a production environment.
- The cache is shared with Internet Explorer which can cause IE to flush your application's cache.
- The cache is file-based meaning it can't be shared across different machines and is also slow.
- There's no way of knowing if the response was retrieved from a cache or a server.
Q: Why not use CacheCow.Client?
A: Well, that's a great question! CacheCow is great for many things but my opinion is that its functionality is spread too thin. It has to maintain functionality for client, server and a lots of different cache implementations resulting in a risk of having more bugs and less attention to details. It also has no support for .NET Standard meaning that it can only run on Windows.
Cashew does not have this problem since we're focusing on one thing, and one thing only, really great HTTP caching! We let others take care of how things are stored which guarantees great results by not having any half-arsed implementations that are not maintained!