-
Notifications
You must be signed in to change notification settings - Fork 172
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
Support mechanism for sticky dials #2019
Labels
enhancement
New feature or request
Comments
plorenz
added a commit
that referenced
this issue
May 6, 2024
plorenz
added a commit
that referenced
this issue
May 7, 2024
plorenz
added a commit
that referenced
this issue
May 17, 2024
Merged
plorenz
added a commit
that referenced
this issue
May 17, 2024
plorenz
added a commit
that referenced
this issue
May 17, 2024
plorenz
added a commit
that referenced
this issue
May 20, 2024
plorenz
added a commit
that referenced
this issue
May 21, 2024
plorenz
added a commit
that referenced
this issue
May 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In some cases, SDKs may wish to pick the best terminator for a given dial and then continue to use the same one, even if smart routing would ordinarily pick a different one. This will help support cases where an application-level session spans multiple requests and all requests must come from the same source.
This should take the form of a new terminator selection strategy so it can be enabled per service.
The text was updated successfully, but these errors were encountered: