[SERVER-52520] Make the ConstructorDestructorActions into a generic pattern Created: 30/Oct/20 Updated: 23/Feb/23 Resolved: 18/Mar/22 |
|
| Status: | Closed |
| 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: | Won't Do | Votes: | 0 |
| Labels: | ben-sa-triage, re-triaged-ticket | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Participants: | |||||||||
| Description |
|
ConstructorDesturctorActions here are a fairly powerful pattern within the ServiceContext. You form a directed graph of actions, then process them all like FILO queue. I propose that we genericize them as something like ActionGraph. This would allow us to use them for new Decorable types, or for more esoteric use cases. Personally, I want to use an extra graph of actions to rephrase server startup and shutdown. (The first graph is ServiceContext construction and destruction.) |
| Comments |
| Comment by Blake Oler [ 26/Jan/23 ] |
|
Keeping this closed. The team doesn't think this is a good idea. |
| Comment by Lauren Lewis (Inactive) [ 18/Mar/22 ] |
|
We haven’t heard back from you for some time, so we're going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket. |