The old LazyDeserialization option should be deprecated. The name LazyDeserialization is incorrect, since the usage and implication of storing objects as binary are far greater than simply deserializing something lazily on replication. The primary use case here is class loader isolation, and in addition it benefits persistent cache stores as well even in a single node environment where there is no RPC going on.

Hence a more descriptive name.