anchor.diff:  Serializers are scoped at the cache level: a cache can have a serializer for its keys and another one for its values.
   All stores of a cache will be using and sharing the same key and value serializer pair.
   
  -=== Copiers
  -
  -As the on-heap store is capable of storing plain java objects as such,
  -it is not necessary to use a costly serialization and deserialization mechanism to copy keys and values when a
  -on-heap store is configured to store by value. For instance, some form of "copy constructor" mechanism is a lot
  -more performant but requires custom code to be able to copy objects.
  -
  -Copiers are specific to the on-heap store: no other store makes use of copiers.
  -
  -By default, the on-heap mappings are stored by reference. The way to store them by value is to configure some copier(s)
  -on it, either key, value or both.
  -
  -=== How is a serializer configured?
  +==== How is a serializer configured?
   
   There are two places where serializers can be configured:
   
  
positive.code: You can optionally implement `java.io.Closeable`. If you do, Ehcache will call `close()` when a cache using such serializer gets disposed of, but *only if*
  Ehcache instantiated the serializer itself.
  
  === Writing a Copier
  
  Implement the following class:
  
  
negative.code: 
  Each cache for which Ehcache instantiated a serializer (i.e.: the serializer was configured by its class name) will have its own instance.
  
  ==== Bundled implementations
  
  By default, cache managers are pre-configured with specially optimized serializers that can handle the following types, in the following order:
  
  