is requestLimitRules really needed at the time of RedisSlidingWindowRequestRateLimiter creation?

[Meyy-DL]

Thank you for all your hard work. Am trying to include your work and realized we must have requestLimitRules in hand before we create RedisSlidingWindowRequestRateLimiter instance. I would like to create vanilla RedisSlidingWindowRequestRateLimiter instance during application startup and inject different rules at different point in the process.

So I was looking at your code and thinking whether we can create vanilla/generic RedisSlidingWindowRequestRateLimiter without tying to limit rules and expose public method to pass in serialized rules later when needed?

Something like
public RedisSlidingWindowRequestRateLimiter(StatefulRedisConnection<String, String> connection)

Highly appreciate your thoughts on my approach.

[mokies]

You should be able to use RedisRateLimiterFactory for this purpose. I have used RedisRateLimiterFactory in the dropwizard module to dynamically create instances of RedisSlidingWindowRequestRateLimiter. While RedisRateLimiterFactory is fairly lightweight to construct the RedisRateLimiterFactory has a small internal cache of instances should this be a concern.

[Meyy-DL]

Looking at the implementation, I guess thats what I was looking for. It would be nice to document these use cases somewhere for future reference. Thanks @mokies!