The main reason for having two versions was to prevent from having to keep
a bunch of classes in memory and mapped to JavaSerializers as well as the
suppress "replace method" check option. Two classes seemed to be much more
memory conscious and performant. But yeah, I hear you on the name.


On Fri, Jan 10, 2014 at 10:45 AM, Nathan Sweet <notifications@github.com>wrote:

> In
> src/com/esotericsoftware/kryo/serializers/ExternalizableMaySerializeSerializer.java:
>
> > @@ -0,0 +1,67 @@
> > +package com.esotericsoftware.kryo.serializers;
> > +
> > +import com.esotericsoftware.kryo.Kryo;
> > +import com.esotericsoftware.kryo.io.Input;
> > +import com.esotericsoftware.kryo.io.Output;
> > +
> > +import java.lang.reflect.Method;
> > +
> > +/**
> > + * Copyright (c) 2012,2013
> > + */
> > +public class ExternalizableMaySerializeSerializer extends ExternalizableSerializer {
>
> This class name is not great. Why not have ExternalizableSerializer be
> able to fall back to JavaSerializer?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/EsotericSoftware/kryo/pull/167/files#r8797792>
> .
>