On 20 October 2011 13:01, Mariano Martinez Peck <[email protected]> wrote: > > > On Thu, Oct 20, 2011 at 1:00 PM, Mariano Martinez Peck > <[email protected]> wrote: >> >> >> On Thu, Oct 20, 2011 at 12:54 PM, Ben Coman <[email protected]> wrote: >>> >>> Mariano Martinez Peck wrote: >>>> >>>> Well...thanks guys. The point is taken. Thanks Philip, Bill and all who >>>> gave feedback and suggestions. We are aware of this and we are already >>>> discussing with Martin possible solutions and analyzing all the things that >>>> has been said in this thread. >>>> We will keep you informed. >>>> >>>> Cheers >>> >>> Just one thing I hadn't seen discussed. Is Fuel possibly a way to >>> exchange objects/data between users/systems ? >> >> Yes >> > > But it doesn't mean it is the best option. Maybe a XML or JSON serializer is > better there... >
If i want speed, i can live with non-portable binary format. If i want portability, compatibility and other blah blah then yeah.. one can always use textual representation of object graph, but don't cry about being slow anymore. > >>> >>> In which case it would have to deal with different systems having >>> different versions of Fuel. >>> >> >> Exactly. It doesn't matter whether the different versions of Fuel happens >> in your own image or in different systems. So yes, it is the same problem. >> Note this is not only a problem for Fuel, but for any serializer which >> does not manages full backward compatibility between versions. >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Best regards, Igor Stasenko.
