[SERVER-41110] Add `connectionTarget` support, using MongoURI format, to Split Horizon Created: 13/May/19 Updated: 08/Jan/24 Resolved: 10/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | ADAM Martin (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Service Arch
|
||||
| Participants: | |||||
| Description |
|
`connectionTarget` isn't necessary to serve the needs of Atlas and Kubernetes. When drivers add support for `connectionTarget`, we'd like to have the entire connection URL sent in this field, instead of just the host-and-port connected to. |
| Comments |
| Comment by Mira Carey [ 10/Sep/20 ] |
|
I think this is a hold over from an earlier design revision in split horizon. In an earlier rev, we were thinking of supporting split horizon in the absence of tls+sni, and this would have been a requirement for that use case. |