In general terms we break up a potentially large object like RemoteTransactionEvent into many smaller BinaryMessages. This is so that if they don't all fit on a single Packet we can easily break them up and put them on multiple packets.
Also note that for the Multicast approach a Packet will generally contain many messages each directed to different members of the cluster. So it would be common for many Ack, Resend and Control messages to all be contained in a single packet.
@author rbygrave This is a subinterface of {@link Message Message} which contains methods toget and set the binary data payload. The setPayloadData()
method sets the value of the payload in the data container without any checking whether the value is valid in any way. Methods for manipulating the address portion of the message are inherited from Message
.
Object instances implementing this interface are just containers for the data that is passed in.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|