[SERVER-68876] SessionWorkflow: use clientStrand only when necessary Created: 16/Aug/22 Updated: 29/Oct/23 Resolved: 11/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Billy Donahue | Assignee: | Billy Donahue |
| 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 2022-10-17, Service Arch 2022-10-31, Service Arch 2022-11-14, Service Arch 2022-11-28, Service Arch 2022-12-12 | ||||||||
| Participants: | |||||||||
| Description |
|
ClientStrand is redundant when using dedicated thread model. The binding to ClientStrand is part of the scheduleNewLoop function currently. |
| Comments |
| Comment by Billy Donahue [ 11/Dec/22 ] |
|
Fixed by |