On Tue, May 08, 2012 at 02:55:47PM -0400, James Carman wrote: > I don't know that you want to get into supporting long-term > serialization support. I would say CM should support transient > serialization (if that makes any sense), such as > marshalling/unmarshalling. If you guarantee long-term serialization > support (reading data from serialized for much later, perhaps by > another version of CM), then we get into the nasty serialization test > cases like Commons Collections has/had. Yuck!
That's the question: What does it mean to support serialization? Is there such a thing as short-term serialization? CM's purpose is not distributed computing. A project could exist with that purpose, and it would indeed choose the "best" possible library to provide the "distribution" functionality. People on this list already said that it should not be the standard (original) Java serialization mechanism. Regards, Gilles --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
