On Tue, Oct 11, 2011 at 5:51 AM, Igor Stasenko <siguctua@gmail.com> wrote:
On 11 October 2011 00:57, Stefan Marr <pharo@stefan-marr.de> wrote:
On 10 Oct 2011, at 23:25, Igor Stasenko wrote:
On 11 October 2011 00:19, Schwab,Wilhelm K <bschwab@anest.ufl.edu>
wrote:
True, but what about reading data from five years ago? I have ten year old Dolphin STB that I can still load.
to my experience a 10 years old data has very small chances to be relevant :)
You might want to reconsider that: Some countries have laws, that regulate how long and what has to be archived:
Switzerland: http://www.itandlaw.ch/html/publikationen/pdf/KMUMagazin04.pdf Germany: http://www.recht-im-internet.de/themen/archivierung.htm
10 years is considered the minimum.
Then how about following idea: help implementing format migration code :)
I think what can be done in Fuel is to have a separate class per each binary format version, so when you do format changes, instead of modifying existing class you creating a new one and put new stuff there. Then at a point of detecting incoming data, it could decide which class to use for deserialization.
Yes, but the problem is that in Fuel we have a flatten design where we group the encoding/decoding of objects in "Cluster" classes. So, the format is not only defined by FLSerializer and FLMaterializer but also with its 20 cluster classes. So it is not that easy...
But that might not be what Pharo or Fuel is supposed to be used for.
-- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525
-- Best regards, Igor Stasenko.
-- Mariano http://marianopeck.wordpress.com