Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add nextQueueStrategy feature to WorkerPoolImpl #132

Merged
merged 1 commit into from
Dec 30, 2017

Conversation

bp-FLN
Copy link
Contributor

@bp-FLN bp-FLN commented Dec 27, 2017

The nextQueueStrategy feature was added in #107, but only for WorkerImpl.
This patch adds the feature also to the WorkerPoolImpl.

@bp-FLN
Copy link
Contributor Author

bp-FLN commented Dec 27, 2017

What about having some common base class for the WorkerImpl and WorkerPoolImpl? Like AbstractWorker or smth similar.
Would save us quite some duplicated code. What do you think @gresrun?

@gresrun
Copy link
Owner

gresrun commented Dec 30, 2017

Florian, I agree, the two should share a common base class. Should have done that work when I first created WorkerPoolImpl but I guess I got lazy!

@gresrun gresrun merged commit 51760f4 into gresrun:master Dec 30, 2017
@bp-FLN bp-FLN deleted the WorkerPoolImpl-nextQueueStrategy branch December 31, 2017 00:35
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