Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.3k
[Messenger] Add messenger rate_limiter docs#17203
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
| ..caution:: | ||
| When a rate limiter is configured on a transport, it will block the whole |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
What about such wordings?
As a rate limiter on a transport will block its worker from consuming when the limit is hit,
you may run a dedicated worker handling such transport to avoid others being blocked.
(Perhaps the english is not perfect) but commenting for the idea
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I think both are good, it is just a personal preference thing. I don't mind changing it, I also don't mind keeping it as is.
ghost commentedNov 23, 2023
Let's merge it after over a year. |
Just came through this, very helpful. |
It took time, but here we go, this is in now. Thank you very much@bobvandevijver. |
Than you@OskarStark |
Documentation forsymfony/symfony#41171