Skip to content

Conversation

@chibenwa
Copy link
Contributor

In this PR I propose 3 kind of event system :

  • the default one : the previous one, revisited. Better failure handling, and package relocation
  • a broadcast based event system : Well if you have global mailbox listeners that will not perform well in a distributed environment.
  • a registered based event system : the scalability limit is the numbers of topics you can handle on your publish subscribe system. It does not support non distributed global Listeners.

Note that the on going discussion about Message Sequence Number handling via the event system is still an open debate ;-)

 - Rely on composition rather than on inheritance for capabilities extension
 - Generalise it so that working on on the event system will be easier
 - Rely on well tested Guava stuff instead of hand craffted collections
@chibenwa
Copy link
Contributor Author

chibenwa commented Nov 4, 2015

I updated the PR after Matthieu comments.

It still needs to be unit test validated ( will take ~ an hour ).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant