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

Provide Intelligent Strategy-based Routing #8

Open
embario opened this issue Mar 22, 2016 · 0 comments
Open

Provide Intelligent Strategy-based Routing #8

embario opened this issue Mar 22, 2016 · 0 comments

Comments

@embario
Copy link
Contributor

embario commented Mar 22, 2016

It may be beneficial to define strategies for having the framework choose an appropriate task for the incoming request, instead of the request choosing the task.

This might be solved by inheriting the AbstractWorkFlow class and defining an input strategy to determine which task is chosen. This would also require changes to the route() call, which should also overload its signature to treat Tasks and WorkFlows as optional parameters. This would give flexibility to the CrowdRouter manager to define the same strategies at a higher level as well, not just within one WorkFlow for choosing which task to perform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant