[SERVER-27254] Add a new component `Registrar` to more cleanly address locking concerns in LegacySession Created: 01/Dec/16 Updated: 06/Dec/22 Resolved: 14/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | ADAM Martin (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Platforms 2017-01-23, Platforms 2017-04-17, Platforms 2017-05-08 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The LegacySession code uses locks to protect a single linked-list tracking connection information. The code which manages that list behind the lock can be cleanly hoisted into a reusable component which also leaves the remaining code more readable. |
| Comments |
| Comment by Mira Carey [ 14/Dec/17 ] |
|
Now that the legacy transport layer is no longer on by default, not worth investing more effort here |