Thank you for your library, along with greenrobot EventBus, it helped us scale our background processing engine in our Android app!
It may be a non-issue but in certain of our state handler sub-classes, we initialize resources (ex: register broadcast receivers, holding a wakelock, etc.). However, for transitions that are not initiated within a state, it would be nice to have a mirror handler method for call(), named terminate() where we can resource clean-up.
Please let me know what you think, maybe I am misusing the APIs and there is already a facility in place for this scenario.
Hi Andrey,
Thank you for your library, along with greenrobot EventBus, it helped us scale our background processing engine in our Android app!
It may be a non-issue but in certain of our state handler sub-classes, we initialize resources (ex: register broadcast receivers, holding a wakelock, etc.). However, for transitions that are not initiated within a state, it would be nice to have a mirror handler method for call(), named terminate() where we can resource clean-up.
Please let me know what you think, maybe I am misusing the APIs and there is already a facility in place for this scenario.
Thanks! -Antoine