[SERVER-27069] Revisit `TransportLayerLegacy::endAllSessions` locking Created: 16/Nov/16 Updated: 08/May/17 Resolved: 08/May/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | ADAM Martin (Inactive) | Assignee: | ADAM Martin (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Platforms 2017-01-23, Platforms 2017-03-06, Platforms 2017-04-17, Platforms 2017-05-08 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The for-loop covering the sessions list does not necessarily need to be processed within the lock. |
| Comments |
| Comment by ADAM Martin (Inactive) [ 01/Dec/16 ] |
|
By changing to this new component, it should remove the locking concern altogether. |