Github user kanakb commented on the pull request:
https://github.com/apache/helix/pull/6#issuecomment-58459371
Email from Kishore:
```
Apologize to throw in another idea into the mix. Why not have additional
methods in the implementation that the agent can invoke on demand based on
annotation?. This extends the way we invoke methods on the statemodel.
For example we have
@Transition(TO=MASTER, FROM=SLAVE)
void fromSlaveTOMaster(Message m, NotificationContext ctx){
}
Can we have something similar as
@Method(name="getProgress")
Response getProgress(Message m, NotificationContext ctx){
}
Helix provides a generic way to invoke a method on a partition. I think
this is more powerful , does not disturb any interfaces and can be extending to
do custom stuff.
Also these methods will not be invoked via ZK, instead the controller can
directly invoke the method on the participant.
Feedback?
```
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
