[SERVER-41624] Fix Split Horizons on Legacy Transport in v3.6 Created: 10/Jun/19 Updated: 29/Oct/23 Resolved: 14/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.14 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | ADAM Martin (Inactive) | Assignee: | ADAM Martin (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Dev Tools 2019-06-17 | ||||
| Participants: | |||||
| Linked BF Score: | 23 | ||||
| Description |
|
Split Horizons was designed and implemented against the modern ASIO based networking stack. Version 3.6 has the option to use the Legacy Transport stack. Split Horizons requires changes to that stack to in order work, when using that stack. |
| Comments |
| Comment by Githook User [ 14/Jun/19 ] |
|
Author: {'name': 'ADAM David Alan Martin', 'email': 'adam.martin@10gen.com', 'username': 'adamlsd'}Message: |