enbility/spine-go

Improve publish / subscribe mechanism for data and events

Opened this issue · 0 comments

Current situation:

  • Right now one can only subscribe to everything
  • Every subscriber will be informed about an event on an independent thread

Ideas to improve this:

  • Option to un-/subscribe to specific/set of EventType
  • Option to provide a channel for receiving events
  • Option to provide a callback functions to be invoked for events

More ideas?