[SERVER-42328] POC pipelining of isMaster and saslStart in AsyncDBClient and NetworkInterfaceASIO Created: 22/Jul/19 Updated: 06/Dec/22 Resolved: 20/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mark Benvenuto | Assignee: | Backlog - Security Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Security
|
| Sprint: | Security 2019-07-29, Security 2019-08-12 |
| Participants: |
| Description |
|
POC sending isMaster and saslStart in the same same send(). Currently, these are processed in two round trips, and with a little bit of change to the client code, lets explore sending and receiving these two commands in a batch instead of sequentially. |
| Comments |
| Comment by Spencer Jackson [ 20/Feb/20 ] |
|
We learned from conversations with Service Architecture that pipelining multiple commands together is harder than expected, and so went with the solution implemented in |