Tags: slawlor/ractor
Tags
Add ability for a factory's internal state to be updated dynamically (#… …333) This allows someone to say reload configeration settings, and internally tear-down and rebuild the factory without fully shutting down and restarting. Some settings are not dynamically settable without tearing down and rebuilding the factory, unless we want to introduce more strong-types to the message type. This includes, unfortunately, the worker builder, queue, and router. For settings on those two, there are two choices. (1) tear down and rebuild the factory or (2) thread in dynamic settings to your router and/or queue protocols such that they can internally change their functionality.
Generalize the factory routing product & add rate limiting support (#331 ) * Generalize the factory routing product to be used in all routing decisions so we can centralize future handling logic related to rate limiting. The goal is to add a general rate limiting offering which can be used at the routing layer, right before sending the job to a worker. * Finish the rate limiting plumbing and add tests around the ratelim wrapper * Added leaky-bucket rate limiter & prep for v0.15 release
Add monitor API back (#317) * Re-add the monitor API, but with an option in the map to save allocations when unused. Additionally move to Option<HashMap> types to save on allocations for regular supervisions (if the actor doesn't supervise anything, we don't need to create the empty map) * Gate monitor API behind a feature, update crate version, add CI coverage on monitors, and update API and README docs
PreviousNext