Good suggestions, I avoided Remote, so as not to be confused with Remote objects.
Cloning is close, however Distributed objects can upgrade to a completely different class implementation and migrate the old implementation object data, way more flexible than Serializable, while utilising the best parts of the serializable object framework. DistributedRecreator? Rather than create or factory it tends to imply recreation. Perhaps a play on Refactor, such as DistributedRefactory? To indicate that change is allowed and expected? Peter. ----- Original message ----- > > Il giorno 23/giu/2014, alle ore 13:24, Peter Firmstone > <j...@zeus.net.au<mailto:j...@zeus.net.au>> ha scritto: > > recreate themselves remotely > > Why not > > * RemoteRecreationFactory > * DistributedCloningFactory > * or a combination of the above? > > This way the name is after the goal of the class, not its > implementation... > > -------------------------------------------------------------------------------------------------------------------- > Stefano Mariani > PhD student @ DISI - Alma Mater Studiorum, Bologna > > s.mari...@unibo.it<mailto:s.mari...@unibo.it> > > stefanomariani.apice.unibo.it<http://apice.unibo.it/xwiki/bin/view/StefanoMariani/> > -------------------------------------------------------------------------------------------------------------------- >
