OK, something I'm still struggling with a bit, and thought I would bounce it out and see if people had thoughts/advice.
I understand the various goals and principles of the project, and obviously the decision came down for content addressed storage... I can see many advantages here, but one potential disadvantage worries me. With a goal of making long-term storage... well, files have been here forever :-) Will we be able to deal with content-addressable storage long term, with the format of attributes, permanodes, etc., etc. I understand that the code can always parse the data, and I could manually parse it file by file from the blob storage, I guess, but with files, anybody with a text editor can do it. There are lots of people that are moving toward text based storage due to longevity of support (and ease of dealing with it), just as an example. Sorry that this is a bit confused... I'm not sure I can articulate my concerns well enough myself (which maybe is an answer right there) :-) I guess it boils down to "do I invest in this solution long term, or stick with more tried and true file based solutions" - I imagine the only response from this audience is "we are", but... -- You received this message because you are subscribed to the Google Groups "Camlistore" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
