Re: Point to point messaging with Ignite

gt; > but you mentioned that* Ignite Queue + [Distributed Countdown Latch + Atomic > Counter] * > > > why need *Distributed Countdown Latch * or* Atomic Counte* here ? As once an > entry item from poll from the queue, then other node can not get the same > entry item. > &g

Re: Point to point messaging with Ignite

Thank you very much! I will write a demo application. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Point-to-point-messaging-with-Ignite-tp1191p2429.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Point to point messaging with Ignite

not get the same entry item. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Point-to-point-messaging-with-Ignite-tp1191p2426.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Point to point messaging with Ignite

;> *make sure only one node* (Node-C or Node-D) could consume this message >> >> >> How to achieve this? If there is a way, does this way is smart enough for >> loading balance? >> >> >> >> >> >> >> -- >> View this message in context: >> http://apache-ignite-users.70518.x6.nabble.com/Point-to-point-messaging-with-Ignite-tp1191p2420.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > >

Re: Point to point messaging with Ignite

use it for computational tasks. IgniteQueue is just a distributed queue, I believe you will have to build the whole infrastructure around it. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Point-to-point-messaging-with-Ignite-tp1191p1223.html Sent from the Apache I

Re: Point to point messaging with Ignite

nSpi.html -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Point-to-point-messaging-with-Ignite-tp1191p1200.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.