README.md in backburner-0.3.0 vs README.md in backburner-0.3.1
- old
+ new
@@ -252,25 +252,26 @@
Since all jobs are persisted in JSON, your jobs must only accept arguments that can be encoded into that format.
This is why our examples use object IDs instead of passing around objects.
### Processing Strategies
-In Backburner, there are actually multiple different strategies for processing jobs
-which are reflected by multiple workers.
+In Backburner, there are several different strategies for processing jobs
+which are reflected by multiple worker subclasses.
Custom workers can be [defined fairly easily](https://github.com/nesquena/backburner/wiki/Defining-Workers).
By default, Backburner comes with the following workers built-in:
| Worker | Description |
| ------- | ------------------------------- |
| `Backburner::Workers::Simple` | Single threaded, no forking worker. Simplest option. |
+| `Backburner::Workers::Forking` | Basic forking worker that manages crashes and memory bloat. |
| `Backburner::Workers::ThreadsOnFork` | Forking worker that utilizes threads for concurrent processing. |
You can select the default worker for processing with:
```ruby
Backburner.configure do |config|
- config.default_worker = Backburner::Workers::Simple
+ config.default_worker = Backburner::Workers::Forking
end
```
or determine the worker on the fly when invoking `work`:
@@ -398,9 +399,10 @@
* [Nathan Esquenazi](https://github.com/nesquena) - Project maintainer
* Kristen Tucker - Coming up with the gem name
* [Tim Lee](https://github.com/timothy1ee), [Josh Hull](https://github.com/joshbuddy), [Nico Taing](https://github.com/Nico-Taing) - Helping me work through the idea
* [Miso](http://gomiso.com) - Open-source friendly place to work
* [Renan T. Fernandes](https://github.com/ShadowBelmolve) - Added threads_on_fork worker
+ * [Daniel Farrell](https://github.com/danielfarrell) - Added forking worker
## Contributing
1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
\ No newline at end of file