On Thu, 27 Dec 2001, Greg McCarroll wrote: > Where does Serialisation end and Persistent Objects > begin?
imo, serialization is just a way to turn an object into a string (and of course get the object back). whether you persist the string, print it, or perform some other operation with or upon it is not directly relevant. > Sure save/load[3] are equivalent to thaw/freeze but what > about lock/unlock[4], how will they integrate with the > Serialisation engines? i don't think a persistence system in an enterprise framework is going to deal with serialization. it's going to be more important in terms of object<->config mapping, and rpc/rmi mechanisms. maybe somebody can show us examples of enterprise software that use object serialization as a primary mechanism for persisting business objects?
