The XOOM Wire component offers various network protocols implemented through XOOM Actors. Since this component may not necessarily be used beyond our own platform components, such as XOOM HTTP, XOOM Cluster and XOOM Directory, we do not document it thoroughly herein. We suggest seeing the Javadoc for more details. You will also find the source code handy.
There are various implementations of TCP support. These are generally used for client-server interactions. Uses can be seen primarily in XOOM HTTP, such as the following.
// generalio.vlingo.xoom.wire.node.Addressio.vlingo.xoom.wire.node.AddressTypeio.vlingo.xoom.wire.node.Host// serverio.vlingo.xoom.wire.channel.RequestChannelConsumerio.vlingo.xoom.wire.channel.RequestResponseContextio.vlingo.xoom.wire.fdx.bidirectional.ServerRequestResponseChannel// clientsio.vlingo.xoom.wire.channel.ResponseChannelConsumerio.vlingo.xoom.wire.fdx.bidirectional.ClientRequestResponseChannel
The purpose of supporting UDP is for multicast, or in other words, broadcast publishing of information. One typical use case is a UDP multicaster service that needs to know what to multicast in behalf of other services. This is the combination of Point-to-Point Channel and Publish-Subscribe patterns, and a form of Message Router. Thus, our UPD multicast is a use-case-specific component, although it can be used for basic UDP multicast of foreknown information.
The XOOM Wire component
MulticastPublisherReader is both a UDP multicast publisher and a TCP socket reader. The client of the
MulticastPublisherReader takes a
ChannelReaderConsumer as a constructor parameter, and when it receives TCP requests it relays the requests to the
ChannelReaderConsumer. Why? Because the
MulticastPublisherReader only knows how to publish two things:
It's own availability, which it does by multicasting its own TCP address, which it holds in its
publisherAddress instance variable. This TCP address is how other services can tell it what to publish, which leads to...
Whatever its client tells it to multicast. This is done via its
ChannelPublisher protocol method
void send(final RawMessage message). These are received via TCP requests, for publishing of the information in the
RawMessage. One example of such is registration by services that want their availability know to other services.
RSocket is currently used only by XOOM Cluster, but we will soon add support in XOOM Streams for high-throughput, low latency streaming over the network. You will find our current RSocket support in: