Yes, we have to work on it. I think version handling should be added wrapping the basic serializer, like other features like a checksum, compression, or encryption. So the class that serializes just worries about serialization.
For example, in the Moose extension we are signing the stream with this prefix: 'FLMoose', version where version represents a two-byte integer. A kind of façade adds this behavior in FLMooseContainerWriter and FLMooseContainerReader, throwing error when either stream doesn't begin with 'FLMoose', or it is a different version. Implementation of FLMooseContainerWriter and FLMooseContainerReader are questionable, but my point is that I believe version is a meta-information about the stream that can be appended optionally. Do you agree? Martin On Sun, Jul 3, 2011 at 6:08 PM, Mariano Martinez Peck <[email protected] > wrote: > > > On Sun, Jul 3, 2011 at 10:23 PM, Francois Stephany < > [email protected]> wrote: > >> >> Do you have differnt versions of Fuel in the two differnt images ? >>> >> >> That was it. >> > > Excellent. > > >> One image had latestVersion (which is 1.4) and the other 1.5 (blessed as >> 'development'). >> >> > Yes, but this is a problem. We should throw a nice error explaining the > situation instead of that. In fact, we are serializing a "version" of Fuel > and we should raise an error in such case. So I am not sure why you received > that. > Martin? > > >> Thanks ! >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > >
