Skip to content

Conversation

lukebakken
Copy link
Collaborator

Supersedes #1704

Thanks for the code @danielmarbach

@lukebakken lukebakken self-assigned this Oct 21, 2024
@lukebakken lukebakken added this to the 7.0.0 milestone Oct 21, 2024
@danielmarbach
Copy link
Collaborator

@lukebakken so do you like this approach?

@lukebakken
Copy link
Collaborator Author

Yeah this is great!

@lukebakken lukebakken force-pushed the rabbitmq-dotnet-client-1682-rate-limiting branch from f15355a to e02734d Compare October 21, 2024 21:37
@lukebakken lukebakken force-pushed the rabbitmq-dotnet-client-1682-rate-limiting branch from ec61e45 to 35f2757 Compare October 22, 2024 14:09
@lukebakken lukebakken marked this pull request as ready for review October 22, 2024 14:55
@lukebakken lukebakken changed the title Spike: Leverage RateLimiting Leverage RateLimiting Oct 22, 2024
@lukebakken lukebakken changed the title Leverage RateLimiting Leverage System.Threading.RateLimiting Oct 22, 2024
* Cosmetic formatting
* Use `RateLimitLease` instead of `IDisposable` in internal classes.
* Move `ThrottlingRateLimiter` to `RabbitMQ.Client` namespace.
* Add the outline of a test for throttling publishes based on outstanding confirms.
* Do not error exit on Windows when `inet_error` is found in logs
* Modify `TestPublisherConfirmationThrottling` to use toxiproxy.
@lukebakken lukebakken force-pushed the rabbitmq-dotnet-client-1682-rate-limiting branch from 35f2757 to f8a18cd Compare October 22, 2024 14:59
@lukebakken
Copy link
Collaborator Author

@danielmarbach - anything to add? Everything looks good to me.

@danielmarbach
Copy link
Collaborator

@danielmarbach - anything to add? Everything looks good to me.

Not really. The only thing that crossed my mind was adding the publish sequence number as Metadata to the rate limiter but that is something that can be done when needed in enhancements

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants