Re: java serialization alternative

Jeff Kesselman wrote:
> Bob Lee wrote:
>> On Sat, Mar 29, 2008 at 3:10 PM, Attila Szegedi <[email protected]>
>> wrote:
>>
>>>  Interesting statement - care to elaborate? I've found that evolving
>>>  the class design is easy with serialization but then, I've been mostly
>>>  adding fields and paid attention that the default value of the field
>>>  is okay for existing serialized object representations. On a single
>>>  object level, it is basically an object-to-(name-value-pair) codec.
>>>  What pitfalls specifically do you have in mind?
>>>
>>
>> Making compatible changes isn't hard. Identifying incompatible
>> changes, for example if a programmer makes a change to a class but
>> forgets to consider serialization, is very tricky.
> This is an issue we will be having to deal with down the line with
> darkstar based apps.  I've been toying mentally with the idea of a tool
> that would take as input a serialized graph, an old code base, and a new
> code base, and allow you to work interactively to solve an
> incompatibilities, hopefully resultign in what is effectively a
> translation script.
 From another pov, think of this as the serialization moral equivalent
of a codebase merge tool

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com