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

We have added default serializers to the 4.2 series here:
hazelcast/hazelcast#17934

There is a problem with backward compatibility. If a user had CustomSerializer for optional in 4.1, in 4.2 there is no way to use their serializers, and Hazelcast will throw java.lang.IllegalArgumentException: [class java.util.Optional] serializer cannot be overridden

Users can basi

currently "option forwardfor" cant't be unset, so there is no way to enable it in the default section and disable it in a particular frontend

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