Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement appropriate patterns for listening/interception/eventing on StateEntry and elsewhere #737

Closed
ajcvickers opened this issue Oct 1, 2014 · 2 comments

Comments

Projects
None yet
3 participants
@ajcvickers
Copy link
Member

commented Oct 1, 2014

Currently we have an IEntityStateListener interface which is used for listening to changes to state entries. (The name should probably change.) Consider if the listener pattern is appropriate or if events or maybe even interception would be a better fit here. Likewise for "lifecycle hooks" throughout the stack.

@rowanmiller rowanmiller added this to the Backlog milestone Oct 8, 2014

@divega

This comment has been minimized.

Copy link
Member

commented Jan 13, 2017

@ajcvickers found this issue in the backlog. Should it be closed as a dupe of #626?

@ajcvickers

This comment has been minimized.

Copy link
Member Author

commented Jan 17, 2017

@divega It probably can be. It was originally a different issue to track what kind of "eventing/interception" mechanism to use throughout the stack, but I think that can be covered when we start work on 626.

@ajcvickers ajcvickers closed this Jan 17, 2017

@ajcvickers ajcvickers removed this from the Backlog milestone Jan 17, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.