CacheManager.Microsoft.Extensions.Logging 1.0.1

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.

Showing the top 20 packages that depend on CacheManager.Microsoft.Extensions.Logging.

Packages Downloads
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

# Release 1.0.1 * Improvements for using CacheManager in ASP.NET Core DI, new overloads for the `IServiceCollection` * Fixed an issue with NuGet references when CacheManager.Core was referenced implicitly only #147 * Extended the `RemoveByHandle` event to also return the removed cache value (if possible). This is not supported for Redis key-events based triggers #144 # Release 1.0.0 **New Things** * New serializer(s) based on [Microsoft.Bond](https://github.com/Microsoft/bond) supporting all three Bond serializers! #127 * Eviction based events reacting on the cache vendor specific evictions see #116 * New event on `BaseCacheManager` with information about which cache handle and why the event was triggered * With this, CacheManager now can sync the cache `Up`. **Minor New Things** * Dictionary Cache Handle now has a timer based eviction loop which should be more reliable. * The Memcached cache handle now finally has a working clear region function #104 * All serializers can be used via Microsoft's configuration extensions as known types (also added to the json schema) * Memcached and Redis cache handles now can be configured to use an already initialized client. The `WithxyzHandle` extension methods have new overloads to pass in the existing client. #118 **Bug Fixes** * #134 Serialization had some issues in some cases with loading the correct Types * #136 when working with absolute expiration, there were some odds when renewing the expiration date * Memcached handle had a bug in version 0.9.3 when configured via xml configuration section, see #118 **Breaking Changes** * UpdateMode `Full` has been removed * Minimum netstandard has been increased to 1.2 from 1.1 for the `Core` package Please report any bugs on github, and feel free to ask questions on either StackOverflow with the `[cachemanager]` tag or on our (moved) homepage http://cachemanager.michaco.net.

.NET Framework 4.5

.NET Standard 1.2

Version Downloads Last updated
2.0.0-beta-1629 6 05/14/2024
1.2.0 3 05/31/2024
1.1.2 5 05/06/2024
1.1.1 4 05/31/2024
1.1.0 4 05/31/2024
1.0.1 3 05/31/2024
1.0.0 6 05/20/2024
1.0.0-beta-1456 5 05/31/2024
0.9.3 4 05/31/2024
0.9.2 3 05/31/2024
0.9.1 3 05/31/2024
0.9.0 2 05/31/2024
0.8.0-beta-1219 2 05/31/2024
0.7.4-beta-1185 4 05/31/2024