[SERVER-75469] Create a data structure to manage buffered socket reads Created: 29/Mar/23 Updated: 03/Aug/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matt Diener (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Sprint: | Service Arch 2023-04-03, Service Arch 2023-04-17, Service Arch 2023-05-01, Service Arch 2023-07-24 |
| Participants: |
| Description |
|
Part of SERVER-73457 |
| Comments |
| Comment by Matt Diener (Inactive) [ 27/Apr/23 ] |
|
The draft PR also provides a more battle-tested implementation of the class itself. It integrates cancellation a little better and takes into account the fact that cancellation complicates the "no parallel operations" rule. |
| Comment by Matt Diener (Inactive) [ 27/Apr/23 ] |
|
The open PR is pretty close. I would recommend using the mock socket from https://github.com/10gen/mongo/pull/12404 |