Make Requests to Either OTP 1 or OTP 2 Depending on Request Type #479
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
miles-grant-ibigroup
added
the
BLOCKED
Collaborator
Author
|
It looks like this has been superseded by/integrated into #470. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As OTP instances don't provide all functionality required by OTP-RR, this PR adds support for routing requests to different servers depending on mode. In this case, flex requests go to OTP-2 instances while non-flex requests go to the OTP-1 instance.
Piggyback PR of #470. However, I think it should be merged into dev after #470 is merged.
The end result: flex and e-scooters in the same itinerary results!
