anchor.diff:  
   So the source side of the connection sends a ServiceSinkReplicationHandler ( be be run on the remote machine )
   
  +
  +```
  +--- !!meta-data #binary
   csp: /replication/out-1/2
   cid: 292323922173575
  +--- !!data #binary
   handler: !ServiceSinkReplicationHandler {
     queueName: out-1,
     wireType: BINARY_LIGHT,
  
positive.code: 
  == Audience
  
  Anyone who wants to get a bit more inside into the data transefer between the remotes host of queue repliaction. This document is not a user functionally guide.
  
  Chronicle Queue Enterprise replication uses an UberHandler. UberHandlers act as message routers, They are  serialised locally then sent to the remote host via tcp/ip, The serialised form of UberHandler looks as follows ( see below )
  
  handler: !net.openhft.chronicle.network.cluster.handlers.UberHandler {
    remoteIdentifier: 1,
    localIdentifier: 2,
    wireType: !WireType BINARY_LIGHT,
    clusterName: global
  }
  
  Chronicle Queue Enterprise typically sends its messages in binary wire format see net.openhft.chronicle.wire.BinaryWire. This is a  binary form of YAML, however to make the messages human readable in this document, we will show the message in text wire  see net.openhft.chronicle.wire.TextWire.
  
  
negative.code: 
  However handshaking messages are send back from the SinkReplicationHandler to the SourceReplicationHandler, one such message is the acknowledgement  message the sinks sends the source. This also you to added code on your sink machine to ensure that message as received by the remote machine and therefore replicated.
  
  ```
  --- !!meta-data #binary
  cid: 292323922173575
  --- !!data #binary
  idx: 0x451600000000
  ns: 10849029994071
  ```
  
  So the handers are as follows
  
  | from	|	to 	| msg sent
  ———————————————————
  | source | sink	    | software.chronicle.enterprise.queue.replication.SinkReplicationHandler
  | sink 	 | source	| software.chronicle.enterprise.queue.replication.SourceReplicationHandler
  
  When using Chronicle Service additional Sink and Source handlers are used to ensure that input queues are replicated before output queues
  
  