Skip to content
This repository has been archived by the owner on Jun 1, 2021. It is now read-only.

Handler-specific behavior stacks #90

Closed
krasserm opened this issue Jul 31, 2015 · 2 comments · Fixed by #201
Closed

Handler-specific behavior stacks #90

krasserm opened this issue Jul 31, 2015 · 2 comments · Fixed by #201
Assignees
Milestone

Comments

@krasserm
Copy link
Contributor

Event-sourcing abstractions distinguish command processing from event processing using different handlers for it. Hence, event-sourced actors should support both, behavior changes for command-handling and for event handling.

From an implementation perspective, two behavior stacks are needed, one for command handling, the other for event handling. The event-handling behavior stack however will not be stored with snapshots and it is the application's responsibility to restore the appropriate behavior during snapshot handling in onSnapshot.

@krasserm krasserm added core and removed core labels Nov 14, 2015
@krasserm krasserm added this to the 0.5 milestone Dec 21, 2015
@krasserm krasserm self-assigned this Dec 21, 2015
@krasserm krasserm added the ready label Dec 21, 2015
@Tvaroh
Copy link
Contributor

Tvaroh commented Dec 26, 2015

Martin, does 'ready' label mean this functionality is available in 0.5 snapshot?

@krasserm
Copy link
Contributor Author

It means ready for implementation.

krasserm added a commit that referenced this issue Jan 20, 2016
krasserm added a commit that referenced this issue Jan 20, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants