[SERVER-77681] Get the proper service context’s decorations based on the operation origin Created: 01/Jun/23 Updated: 05/Jan/24 Resolved: 05/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Antonio Fuschetto |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding NYC
|
| Participants: |
| Description |
|
Some service context's decorations have a different implementation for router and router role respectively (e.g., LogicalSessionCache). Getter functions should transparently return the proper implementation based on the origin of the request (i.e., coming from the public or private port). |
| Comments |
| Comment by Antonio Fuschetto [ 05/Jan/24 ] |
|
The goal of this ticket was to implement a very generic mechanism to get any decoration. However, now ServiceContext and Service provide a way to get decorations based on the role. |
| Comment by Antonio Fuschetto [ 05/Jan/24 ] |
|
The goal of this ticket was to implement a very generic mechanism to get any decoration. However, now ServiceContext and Service provide a way to get decorations based on the role. |
| Comment by Billy Donahue [ 12/Sep/23 ] |
|
I think it would be appropriate to rephrase this ticket in terms of ServiceContext (server-wide state) and Service (per-service state). There are decorations of ServiceContext that should become decorations of Service. |