It uses zookeeper for messaging. The goal of this feature is to guarantee successful deliver of message. For example, you can send a message even if the node is down and it can process it when it comes back up. Other feature is to ensure that the message is processed by the recipient only if the send criteria matches when is message is received. For example, you can say things like
* Only the current participant should process it, which means if the participant dies and comes back up it can ignore that message. * It should be slave for a resource, if its state has changed after the sender sends message it can ignore the message. This feature should not be used to achieve low latency or high throughput messaging between components. We do have plans to provide a java nio based mechanism to communicate between various components but havent scoped it thanks, Kishore G On Tue, May 21, 2013 at 9:29 AM, Erwin Karbasi <[email protected]> wrote: > Hello All, > > Which protocol/mechanism/framework Helix uses for sending messaging among > nodes as described here: > http://helix.incubator.apache.org/tutorial_messaging.html > > Thanks, > Erwin Karbasi > AT&T, Senior Software Architect >
