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

Client: Use workers for private jobs #128

Closed
indyjo opened this issue Jan 19, 2017 · 3 comments
Closed

Client: Use workers for private jobs #128

indyjo opened this issue Jan 19, 2017 · 3 comments
Labels
client This issue involves the BitWrk client software enhancement

Comments

@indyjo
Copy link
Owner

indyjo commented Jan 19, 2017

No description provided.

@indyjo indyjo added client This issue involves the BitWrk client software enhancement labels Jan 19, 2017
@indyjo indyjo added this to the BitWrk 0.6.0 Ease of Use milestone Jan 19, 2017
@indyjo
Copy link
Owner Author

indyjo commented Jan 29, 2017

BitWrk could be more efficient if it were possible to use own workers without offering them publicly. Local workers should always have precedence when dispatching work.

@indyjo
Copy link
Owner Author

indyjo commented Apr 3, 2017

Buys should be eligible for local dispatch right until they're placed on BitWrk, not only until they receive clearance.

@indyjo indyjo reopened this Apr 3, 2017
@indyjo
Copy link
Owner Author

indyjo commented Apr 14, 2017

Followup issue: #137

@indyjo indyjo closed this as completed Apr 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client This issue involves the BitWrk client software enhancement
Projects
None yet
Development

No branches or pull requests

1 participant