CacheManager.Core 0.9.3
CacheManager is an open source caching abstraction layer for .NET written in C#. It supports various cache providers and implements many advanced features. The Core library contains all base interfaces and tools. You should install at least one other CacheManager package to get cache handle implementations.
Showing the top 20 packages that depend on CacheManager.Core.
| Packages | Downloads |
|---|---|
|
CacheManager.Microsoft.Extensions.Configuration
CacheManager extension package to use Microsoft.Extensions.Configuration to configure the CacheManager instance. CacheManager is an open source caching abstraction layer for .NET written in C#. This is the ASP.NET Core configuration integration package.
|
4 |
|
CacheManager.Microsoft.Extensions.Configuration
CacheManager extension package to use Microsoft.Extensions.Configuration to configure the CacheManager instance. CacheManager is an open source caching abstraction layer for .NET written in C#. This is the ASP.NET Core configuration integration package.
|
5 |
|
CacheManager.Microsoft.Extensions.Configuration
CacheManager extension package to use Microsoft.Extensions.Configuration to configure the CacheManager instance. CacheManager is an open source caching abstraction layer for .NET written in C#. This is the ASP.NET Core configuration integration package.
|
6 |
|
CacheManager.Microsoft.Extensions.Configuration
CacheManager is an open source caching abstraction layer for .NET written in C#. This is the ASP.NET Core configuration integration package.
|
5 |
|
CacheManager.Microsoft.Extensions.Configuration
CacheManager is an open source caching abstraction layer for .NET written in C#. This is the ASP.NET Core configuration integration package.
|
7 |
|
CacheManager.Microsoft.Extensions.Logging
CacheManager extension package to work with Microsoft.Extensions.Logging as logging provider. CacheManager is an open source caching abstraction layer for .NET written in C#. The ASP.NET Core logging provides a bridge to the Microsoft.Extensions.Logging framework.
|
4 |
|
CacheManager.Microsoft.Extensions.Logging
CacheManager extension package to work with Microsoft.Extensions.Logging as logging provider. CacheManager is an open source caching abstraction layer for .NET written in C#. The ASP.NET Core logging provides a bridge to the Microsoft.Extensions.Logging framework.
|
5 |
|
CacheManager.Microsoft.Extensions.Logging
CacheManager extension package to work with Microsoft.Extensions.Logging as logging provider. CacheManager is an open source caching abstraction layer for .NET written in C#. The ASP.NET Core logging provides a bridge to the Microsoft.Extensions.Logging framework.
|
6 |
|
Ocelot
Ocelot Api Gateway
|
5 |
|
Ocelot
This project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.
|
4 |
|
Ocelot
This project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.
|
5 |
|
Ocelot
This project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.
|
6 |
|
Ocelot
This project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.
|
11 |
This release has some new features and fixes.
**New Features**
* Exists method to check if the key exists without actually retrieving it (if supported by the cache vendor) #46
* Added more "knownTypes" to Microsoft.Extensions.Configuration based CacheManager configuration's json schema #125 #123
* for the Microsoft.Extensions.Caching.MemoryCache based cache handle
* Protobuf serializer
* GzJson serializer
* Allow Memcached and Redis cache handles to use pre existing cache clients. The clients can now be passed into the configuration methods `WithRedisConfiguration`, `WithMemcachedHandle`. #118
**Other Changes**
* Instead of CacheManagerConfiguration now ICacheManagerConfiguration will be used everywhere (more injection friendly)
* Improved validation at configuration time in case a cache handle requires a serializer, but none is defined (only net core target as full framework falls back to binary).
* custom serialization logic for memcached to use our cache serializers instead of the build in binary.
* Added overload to configure binary serializer settings during configuration.
**Bug fixes**
* Validate expiration timeout not being in the past #74
* Changed update mechanism in the redis implementation to use a version field #109
* Fixed a bug where the mechanic in CacheManager which adds a key/value to other cache handles does not correctly apply expiration settings based on the cache handle configuration when it comes from Redis.
* other minor things
Please report any bugs or issues you find on [github](https://github.com/MichaCo/CacheManager)
.NET Framework 4.0
- No dependencies.
.NET Standard 1.1
- System.Reflection (>= 4.1.0)
- System.Runtime.InteropServices (>= 4.1.0)
- System.Runtime.Extensions (>= 4.1.0)
- System.Text.Encoding (>= 4.0.11)
- System.Threading (>= 4.0.11)
- System.Collections.Concurrent (>= 4.0.12)
- System.Diagnostics.Debug (>= 4.0.11)
- System.Diagnostics.Tools (>= 4.0.1)
- System.Linq (>= 4.1.0)
- System.Collections (>= 4.0.11)
- System.Globalization (>= 4.0.11)
.NET Framework 4.5
- No dependencies.
| Version | Downloads | Last updated |
|---|---|---|
| 2.0.0-beta-1629 | 7 | 05/06/2024 |
| 1.2.0 | 1 | 05/31/2024 |
| 1.1.2 | 3 | 05/31/2024 |
| 1.1.1 | 5 | 05/31/2024 |
| 1.1.0 | 3 | 05/31/2024 |
| 1.0.1 | 3 | 05/31/2024 |
| 1.0.0 | 3 | 05/31/2024 |
| 0.9.3 | 4 | 05/31/2024 |
| 0.9.2 | 2 | 05/31/2024 |
| 0.9.1 | 3 | 05/31/2024 |
| 0.9.0 | 2 | 05/31/2024 |
| 0.8.0 | 2 | 05/31/2024 |
| 0.7.4 | 2 | 05/31/2024 |
| 0.7.3 | 3 | 05/31/2024 |
| 0.7.2 | 2 | 05/06/2024 |
| 0.7.1 | 3 | 05/31/2024 |
| 0.7.0 | 3 | 05/31/2024 |
| 0.6.1 | 2 | 05/31/2024 |
| 0.6.0 | 3 | 05/31/2024 |
| 0.5.0 | 4 | 05/31/2024 |
| 0.4.4.1 | 4 | 05/31/2024 |
| 0.4.4 | 4 | 05/31/2024 |
| 0.4.3 | 7 | 05/31/2024 |
| 0.4.2 | 3 | 05/31/2024 |
| 0.4.1 | 4 | 05/31/2024 |
| 0.4.0 | 2 | 05/31/2024 |
| 0.3.1 | 4 | 05/31/2024 |
| 0.3.0 | 3 | 05/31/2024 |
| 0.2.0 | 4 | 05/31/2024 |
| 0.1.5 | 4 | 05/06/2024 |