[SERVER-81300] Refactor ScopedBaseDDLLock to use a NamespaceString Created: 21/Sep/23 Updated: 23/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mathis Bessa | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | ntdi_releasability | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Participants: | |||||||||
| Story Points: | 2 | ||||||||
| Description |
|
ScopedBaseDDLLock private constructor third parameter is called StringData resName which stands for Resource Name. This resource name is passed and stored under _resourceName which is then ONLY used to as a second parameter of lock and unlock of the _lockManager. For these two methods, the third parameter which accepts a StringData is marked as ns which makes me think this could accept a NamespaceString. |