1. I understand "Memento" is an interface and "ReflectiveMemento" - an implementation
2. Isn't just "Memento" too generic? DistributedObjectMemento? SerializableMemento? (to indicate implementations should support standard serialization)? 3. A little different issue - did u find a way to serialize cycles in the object graph? Right now SerialReflectionFactory has the same issues as writeReplace()/ readResolve() Thanks, Michal On Thursday 26 of June 2014 20:53:03 Peter wrote: > Any objections to calling it Momento? > > ----- Original message ----- > > > You're sharp, so it is, that's a good one. > > > > ----- Original message ----- > > > > > It really is a Memento. Isn't it? > > > > > > Michal > > > > > > 23 cze 2014 13:24 "Peter Firmstone" <j...@zeus.net.au> napisał(a): > > > > Distributed object use SerialReflectionFactory to recreate themselves > > > > remotely using one of their public constructors, a static factory > > > > method or builder object, however one thing about > > > > SerialReflectionFactory bothers me. > > > > > > > > SerialReflectionFactory is named after it's implementation, that is, > > > > it uses reflection. At some point in time, we might decide we want > > > > to use something other than reflection, in that case, the name would > > > > be inappropriate. > > > > > > > > How does DistributedObjectFactory sound? > > > > > > > > Has anyone got a better name? > > > > > > > > Regards, > > > > > > > > Peter. --
