Project Summary
A worker pool is a very common pattern, and they exist in the standard libraries for many languages. The idea is simple: submit some sort of closure to a service which commits to running the closure in the future in some thread. Normally the work is shared out among many different threads and in the absence of anything fancier, one assumes a first-come-first-served queue of closures.
RabitMQ's codebase contains exactly such a worker pool. A description of RabbitMQ's worker pool can be found here: http://www.lshift.net/blog/2010/03/29/on-the-limits-of-concurrency-worker-pools-in-erlang
This is an extension of this code.
In a Nutshell, worker_pool...
- ...
- ...
- ...
-
...
took an estimated 1 years of effort (COCOMO model)
starting with its first commit in August, 2010
ending with its most recent commit over 7 years ago
Quick Reference
Apache License 2.0
Permitted
Place Warranty
Sub-License
Private Use
Use Patent Claims
Commercial Use
Modify
Distribute
Forbidden
Hold Liable
Use Trademarks
Required
Include Copyright
State Changes
Include License
Include Notice
These details are provided for information only. No information here is legal advice and should not be used as such.
This Project has No vulnerabilities Reported Against it
Did You Know...
-
...
Black Duck offers a free trial so you can discover if there are open source vulnerabilities in your code
-
...
check out hot projects on the Open Hub
-
...
there are over 3,000 projects on the Open Hub with security vulnerabilities reported against them
-
...
data presented on the Open Hub is available through our API
30 Day SummaryApr 9 2018 — May 9 2018
|
12 Month SummaryMay 9 2017 — May 9 2018
|
