Class ReplicatorMessageSerializer

    • Constructor Detail

      • ReplicatorMessageSerializer

        public ReplicatorMessageSerializer​(ExtendedActorSystem system)
    • Method Detail

      • GetManifest

        public java.lang.String GetManifest()
      • GetSuccessManifest

        public java.lang.String GetSuccessManifest()
      • NotFoundManifest

        public java.lang.String NotFoundManifest()
      • GetFailureManifest

        public java.lang.String GetFailureManifest()
      • SubscribeManifest

        public java.lang.String SubscribeManifest()
      • UnsubscribeManifest

        public java.lang.String UnsubscribeManifest()
      • ChangedManifest

        public java.lang.String ChangedManifest()
      • DataEnvelopeManifest

        public java.lang.String DataEnvelopeManifest()
      • WriteManifest

        public java.lang.String WriteManifest()
      • WriteAckManifest

        public java.lang.String WriteAckManifest()
      • ReadManifest

        public java.lang.String ReadManifest()
      • ReadResultManifest

        public java.lang.String ReadResultManifest()
      • StatusManifest

        public java.lang.String StatusManifest()
      • GossipManifest

        public java.lang.String GossipManifest()
      • WriteNackManifest

        public java.lang.String WriteNackManifest()
      • DurableDataEnvelopeManifest

        public java.lang.String DurableDataEnvelopeManifest()
      • DeltaPropagationManifest

        public java.lang.String DeltaPropagationManifest()
      • DeltaNackManifest

        public java.lang.String DeltaNackManifest()
      • fromBinary

        public java.lang.Object fromBinary​(byte[] bytes,
                                           java.lang.String manifest)
        Description copied from class: SerializerWithStringManifest
        Produces an object from an array of bytes, with an optional type-hint.

        It's recommended to throw in fromBinary if the manifest is unknown. This makes it possible to introduce new message types and send them to nodes that don't know about them. This is typically needed when performing rolling upgrades, i.e. running a cluster with mixed versions for while. NotSerializableException is treated as a transient problem in the TCP based remoting layer. The problem will be logged and message is dropped. Other exceptions will tear down the TCP connection because it can be an indication of corrupt bytes from the underlying transport.

        Specified by:
        fromBinary in class SerializerWithStringManifest