Skip to content

Conversation

@nevans
Copy link
Collaborator

@nevans nevans commented Oct 28, 2015

Use ruby's autoload (thread-safe since 2.0) instead of require sprinkled here and there.

Based on #143, because the namespacing changes a lot in there.

joshuaflanagan and others added 8 commits October 26, 2015 18:16
Many custom configuration loaders will retrieve the
configuration from an external resource. `Resque::Pool`
asks the loader for the latest configuration roughly
once per second. You may want to reduce load on your
external resource by caching the value, and only
really fetching the latest configuration after a
specific amount of time has passed.

Instead of forcing each configuration loader author
to re-write (and test) this logic, we provide `Resque::Pool::ConfigThrottle`.

See the spec for full details of its behavior.
n.b. this cleans up the resque/pool/pooled_worker monkeypatching a little bit.
It runs only on `Resque::Pool.new` now.
@nevans nevans mentioned this pull request Oct 28, 2015
@nevans
Copy link
Collaborator Author

nevans commented Dec 4, 2018

Do not want.

@nevans nevans closed this Dec 4, 2018
@nevans nevans deleted the autoloads branch October 25, 2022 15:25
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.

3 participants