That makes sense. Now I am using ignite.GetBinding() from within the main() function
In the main function, I am populating a vector of strings and calling RunAsync() three times. The ignite node within the binary is able to process the string but the other two ignite nodes report the same IgniteException of job not being registered. Looks like the example binary is able to communicate with the two ignite server nodes but those two nodes have no idea about the PrintWords' Call method. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
