Expected Behaviour
I'm using limits for some distributed processing tools. However one of the services that we use has a limit of "100 concurrent requests", rather than a window based limit.
I found #279 which shows an example of implementing a ConcurrentRateLimitItem, In our testing this works as expected and we've ended up just using this example ourselves.
Do you think it'd be a good idea to add this as an available rate limit type and document it? Maybe this kind of limit is needed quite often. I'm not sure if it makes more sense conceptually for this to be a new Strategy, or just a rate limit type as in the linked issue which can be used with any strategy.
Expected Behaviour
I'm using limits for some distributed processing tools. However one of the services that we use has a limit of "100 concurrent requests", rather than a window based limit.
I found #279 which shows an example of implementing a ConcurrentRateLimitItem, In our testing this works as expected and we've ended up just using this example ourselves.
Do you think it'd be a good idea to add this as an available rate limit type and document it? Maybe this kind of limit is needed quite often. I'm not sure if it makes more sense conceptually for this to be a new Strategy, or just a rate limit type as in the linked issue which can be used with any strategy.