These are chat archives for atomix/atomix
That API has both:
unicast for asynchronous direct messages
broadcast for broadcasting to all subscribers
send for synchronous direct (request-reply)
The change in that PR is just to allow multiple subscribers on a single node. The previous implementation only allowed one per-topic per-node. This API is really modeled on the Vert.x event bus to which I was once upon a time a committer (still am?)
So, the two messaging APIs actually exposed to users are the
ClusterMessagingService which generally requires node information (a
NodeId to which to send a message) and the
ClusterEventingService which replicates topics/subscribers. Both support those three messaging paradigms.
betarelease this week. Thereafter, the review process for Atomix 2.1 will be reinstituted, and API changes will be kept to a minimum. In January will be some release candidates and perhaps the final release.