make the serialization system backwards compliant

[GoogleCodeExporter]

It should load the resources even if the data description changed.

It should cover the following cases:
 - classes can change their names
 - class members can be added
 - class members can be removed

First of all - all members need to reside in a clearly marked stream segment, 
that is prefixed with the segment size, so that if for instance a class memeber 
is removed from the class definition, we know how much data from the stream we 
should skip in order to get to the next one.

Also - right now the entire process is very nested - if a member is a complex 
structure, its members are stored in the stream in place etc.
And there's also the dependency mapping issue. Make sure that's not gonna break.

Original issue reported on code.google.com by ptroc...@gmail.com on 3 Dec 2011 at 2:17

[GoogleCodeExporter]

Original comment by ptroc...@gmail.com on 4 Dec 2011 at 1:39

• Changed state: Started

[GoogleCodeExporter]

Original comment by ptroc...@gmail.com on 1 May 2012 at 12:33

• Changed state: Fixed