Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

startTime property in RateLimiter #752

Open
walec51 opened this issue Nov 18, 2019 · 3 comments · May be fixed by #2100
Open

startTime property in RateLimiter #752

walec51 opened this issue Nov 18, 2019 · 3 comments · May be fixed by #2100
Assignees

Comments

@walec51
Copy link
Contributor

walec51 commented Nov 18, 2019

I propose to add a startTime property to RateLimiterConfig so that we can set from when does a RateLimiting period start. This is necessary if someone wants to user RateLimiter both on his server and client. If you have your clocks in synce then with this property one could make limit period overlap on the server and client.

@RobWin
Copy link
Member

RobWin commented Nov 19, 2019

Hi,

yes, good idea.

@RobWin
Copy link
Member

RobWin commented Jan 29, 2020

FYI @storozhukBM

@storozhukBM storozhukBM self-assigned this Jan 29, 2020
@storozhukBM storozhukBM added this to the 1.3.0 milestone Jan 29, 2020
@RobWin RobWin removed this from the 1.3.0 milestone Apr 22, 2020
injae-kim added a commit to injae-kim/resilience4j that referenced this issue Jan 23, 2024
@injae-kim injae-kim linked a pull request Jan 23, 2024 that will close this issue
injae-kim added a commit to injae-kim/resilience4j that referenced this issue Jan 23, 2024
@injae-kim
Copy link

Hi! I created PR #2100 to fix this issue. PTAL when you have some times~ thanks! 😃

injae-kim added a commit to injae-kim/resilience4j that referenced this issue Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants