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

Use of RouteAggregator by Task services for waypoint routes #24

Open
derekkingston opened this issue Jun 9, 2017 · 0 comments
Open
Assignees

Comments

@derekkingston
Copy link
Collaborator

Rather than have Task services request waypoints directly from the route planner(s), Task services should instead make a single request to the RouteAggregator and wait for the single response. This greatly simplifies state transition logic for Task services. In addition, proper handling of heterogeneous vehicles is handled by the RouteAggregator and duplicate functionality need not be in each Task service.

@derekkingston derekkingston self-assigned this Jun 9, 2017
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

No branches or pull requests

1 participant