While coding this up i realized that udp had no sessions so to do a two part request response the messages need to be tagged in some way to correlate the requests.
One way to go forward is to do something like seda or async and separate our connection from few processing. Another route is ditch udp and go to where request reply is more straight forward . On Monday, June 13, 2016, Edward Capriolo <[email protected]> wrote: > Hey all, > > Quick development update. Currently the ActiveGossipThread connects and > sends a message and the protocol disconnects without waiting for a > response. The effect of this is that if there is a detectable condition > like "mismatched cluster name" this result can not be communicated back. It > looks simple to add a return to the payload so I am going to tackle that. > > Thanks, > Edward > -- Sorry this was sent from mobile. Will do less grammar and spell check than usual.
