Norbert Hartl wrote:
Am 10.02.2012 um 19:51 schrieb Igor Stasenko:
On 10 February 2012 19:27, Eliot Miranda <eliot.miranda@gmail.com> wrote:
But if you choose this route let me strongly suggest you use the zip file format. Its very useful with Monticello mcz's to be able to pick them apart using unzip.
yes but then it makes the whole thing completely orthogonal to Fuel. because in zip you can have one file to hold serialized stuff, in another your metadata and whatsoever.. i mean, you can organize your data packaging yourself, without forcing fuel to support anything related to metadata.
and i think this is right direction.
So. I think it is useless to try extending fuel with metadata. if people want to have metadata, they should make it by own, in the way they see fit. I think fuel should do one thing : serialize/materialize stuff. Lets not turn it into "i can do everything to please you" library.
+1
Fuel does what it does. Having a fuel with metadata is just a customized format. In the end it is all streams. You can open a file read the metadata and then hand over the stream to fuel. I don't see any need to tweak fuel for that. Changing it to be able to read multiple roots sounds great but has the potential for e.g. doubling objects and all sorts (if I understand it correct).
Norbert
Using a standard container is better resuse and design - but maybe you still want to specify exactly the format of a file ending in "*.fuel". Is it _always_ a zip file or do you look for the zipfile magic number and if that is not there revert to it being a single fuel stream. cheers, -ben