[SERVER-54155] Standardize onCreate/onDestroy pattern for Decorations Created: 29/Jan/21 Updated: 23/Mar/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: | 1 |
| Labels: | re-triaged-ticket, servicearch-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||
| Participants: | |||||||||||||
| Story Points: | 1 | ||||||||||||
| Description |
|
We have a decently useful pattern for create/destroy hooks for ServiceContext here. Unfortunately, the pattern for ClientObservers is much less rigorous and requires defining a ServiceContext hook to make another hook like here. That can cause trouble when we make clients in ServiceContext create/destroy hooks. We should split apart ClientObservers and extend the stronger pattern to Clients and OperationContexts separately. |
| Comments |
| 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. |