[SERVER-68861] provide class hierarchy for SessionCatalog, MongoDSessionCatalog, and RouterSessionCatalog Created: 16/Aug/22 Updated: 15/Nov/22 Resolved: 15/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Shin Yee Tan |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Execution Team 2022-10-17, Execution Team 2022-10-31, Execution Team 2022-11-14, Execution Team 2022-11-28 | ||||||||
| Participants: | |||||||||
| Description |
|
These three classes are generally used to manage logical sessions, backed by the config.sessions collection on mongod: It would make the relationships among these classes easier to understand if we unified them in a class hierarchy. |
| Comments |
| Comment by Shin Yee Tan [ 15/Nov/22 ] |
|
Deciding to close because the relationships of these classes don't necessarily fit into a class hierarchy. Other efforts such as |