[SERVER-51701] Formalize relationship between ingress Sessions and Clients Created: 16/Oct/20 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | sa-remove-fv-backlog-22 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Backwards Compatibility: | Fully Compatible |
| Participants: | |
| Story Points: | 5 |
| Description |
|
Currently, every Client may have a Session (here). I think we should formalize this relationship:
This will make it easier to work with ingress Client instances and allow us to access decorations deeper into the transport infrastructure. Acceptance criteria: The relationship between client and session objects is clear and hard to misuse and properly encoded in the type system.
|