It would be nice to have a separated package per cache provider, so for instance:
- CacheAdapter.AppFabricCache
- CacheAdapter.Memcached
In this way every NuGet package take dependency only on the technology it needs, AppFabric will only take dependency on CacheAdapter.Core and ServerAppFabric.Client.
Probably the Memory and Web implementation could be integrated in the CacheAdapter.Core because it only relies on .NET framework.
CacheManager is making something similar CacheManager.AppFabricCache
Also from Todd Carter
I agree with Michael - I really do not want to install 3-4 additional packages which I do not use and then get deployed. There should be a core with memory only and then a CacheAdapter.Redis CacheAdapter.AppFabric etc packages. I am not aware of anyone whom would choose to use multiple adapters in the same project so why deploy them all at once. To me this is not minor and in fact is blocking our using this package.
This issue has been migrated from the original bitbucket issue#32 on 13-09-2017
It would be nice to have a separated package per cache provider, so for instance:
In this way every NuGet package take dependency only on the technology it needs, AppFabric will only take dependency on CacheAdapter.Core and ServerAppFabric.Client.
Probably the Memory and Web implementation could be integrated in the CacheAdapter.Core because it only relies on .NET framework.
CacheManager is making something similar CacheManager.AppFabricCache
Also from Todd Carter
I agree with Michael - I really do not want to install 3-4 additional packages which I do not use and then get deployed. There should be a core with memory only and then a CacheAdapter.Redis CacheAdapter.AppFabric etc packages. I am not aware of anyone whom would choose to use multiple adapters in the same project so why deploy them all at once. To me this is not minor and in fact is blocking our using this package.
This issue has been migrated from the original bitbucket issue#32 on 13-09-2017