[SERVER-63676] Investigate the need for session_asio.cpp ASIOSession blocking calls Created: 15/Feb/22 Updated: 06/Dec/22 Resolved: 05/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Morilha (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | sa-remove-fv-backlog-22 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Participants: | |||||||||
| Story Points: | 3 | ||||||||
| Description |
|
The C++ ASIO library provides both synchronous and asynchronous network operations, where the main difference is a synchronous call blocks the thread calling to it while the asynchronous has its callback eventually called to. To make it even worse, some methods depend on an internal boolean flag to decide which one to call. This is a slippery slope for first-time readers. This is a time boxed investigation effort to understand, document and potentially change the behavior. I would like to believe blocking calls aren't pervasively used, and if so, could be retired to their own codepath / file / class... |
| Comments |
| Comment by Matt Diener (Inactive) [ 05/Oct/22 ] |
|
Trying to clean up some of the duplicate work items. This is in scope of the design and is likely to be addressed. |
| Comment by Blake Oler [ 29/Aug/22 ] |
|
Optimistically placing this into PM-2768. |
| Comment by Connie Chen [ 24/Aug/22 ] |
|
Re-assigning back to the service arch backlog user and throwing it into triage |