[SERVER-45982] Separate RequestState concept from NetworkInterfaceTL::CommandState Created: 05/Feb/20 Updated: 29/Oct/23 Resolved: 13/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Benjamin Caimano (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 | ||||||||
| Sprint: | Service Arch 2020-02-10, Service Arch 2020-02-24 | ||||||||
| Participants: | |||||||||
| Description |
|
The pathway into and out of onAcquireConn(...) represent the networking precursor of a callback to a command response. We should separate this piece so that we can build around it without concern for connection reuse or error handling. |
| Comments |
| Comment by Githook User [ 10/Feb/20 ] |
|
Author: {'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}Message: |