Here is an issues with detailed description: NekR/offline-plugin#77

Please describe the problem you are trying to solve
I would like to evict entries based on their creation time. I want to evict the oldest ones first.

Please describe the desired behavior
Basically FIFO eviction. I would like to specify directly in the configuration something like:

<eviction eviction-policy="FIFO" max-size-policy="PER_NODE" size="5000"/>

**Describe alte

Currently we have a mix of:

• Out of memory error.
• Out of memory error
• out of memory error
• out of memory
• out of memory.
• out of memory [some context]

All these should be adjusted to use the same wording for consistency and it should also make the executable a little bit smaller 😄

Currently we don't have any mechanism to limit the maximum number of clients that could be handled simultaneously.

This feature should be designed properly. Here is some clue: https://redis.io/topics/clients#maximum-number-of-clients

Hi - We're trying to use the caching in an environment were the Redis endpoints are discoverable via a service registry (consul). It would be great if the AddEasyCaching configuration action had access to the service provider.

Do you have any recommendation to best active this with what is available today, given that the service (per RedisEndpoints) below is registered elsewhere, and it bei

Even though this isn't super critical, this might help with addressing https://stackoverflow.com/questions/57938081/blazor-preview-9-mono-wasm-memory-access-out-of-bounds-max-string-size-for-dotn