[SERVER-45858] Annotate OperationContext with Command details Created: 30/Jan/20 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | sa-remove-fv-backlog-22 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
The Command infrastructure uses a combination of OperationContext, OpMsgRequest, and CommandInvocation, all by pointer or reference, for many function signatures. However, both the OMR and the CI have well defined lifetimes and factory functions. We can annotate the OperationContext with pointers to the other two types and reset those pointers when the underlying memory goes out of scope. This will allow us to tremendously simplify the api around commands. |