You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we add synchronous methods Get/GetOrSet, etc it allows CacheTower functionality to be used outside of asynchronous contexts.
How would you use/interact with the feature? (if applicable)
Exactly the same as the async versions - just synchronously :) Other common implementations E.g. IDistributedCache have both synchronous and asynchronous flavors of methods.
Notes
I wanted to add CacheTower to my stack and for starters - use it for caching expression trees. However, this is all synchronous work - so I went with IMemoryCache/IDistributedCache instead for now.
The text was updated successfully, but these errors were encountered:
While I do understand the difficulty as async-over-sync is extremely problematic, supporting synchronous paths for Cache Tower would practically double the amount of code across the project and the maintenance overhead along with it. Every cache layer would need to support it, every extension too.
I'm not saying I won't support synchronous methods in the future but currently it isn't on my roadmap.
What problem does the feature solve?
If we add synchronous methods Get/GetOrSet, etc it allows CacheTower functionality to be used outside of asynchronous contexts.
How would you use/interact with the feature? (if applicable)
Exactly the same as the async versions - just synchronously :) Other common implementations E.g. IDistributedCache have both synchronous and asynchronous flavors of methods.
Notes
I wanted to add CacheTower to my stack and for starters - use it for caching expression trees. However, this is all synchronous work - so I went with IMemoryCache/IDistributedCache instead for now.
The text was updated successfully, but these errors were encountered: