Hi, it's just a matter on how you want to model your data, what kind of relationship you want to set up between your items, and how you want to represent your data. If all you want is e.g. to archive your data, then creating a permanode for the directory is enough, as the files are still reachable/searchable through the directory (static-set) relationship (that is, once you have found the directory's permanode).
hth, Mathieu On 11 July 2016 at 15:41, <[email protected]> wrote: > Hello all... > > Another newbie with a list of newbie questions. > > Don't want to inundate things, so figured I would start with just one :-) > > Why would something ever not be a permanode? > > Every time I think I have my head wrapped around permanodes, I get confused > again. > > The FUSE interface makes all files permanodes (which makes sense to me)... > but if I camput a directory, then just the directory is (which has > implications for viewing the files, etc.) > > Guess I'm just lost. > > Thoughts? > > Thanks, > Bruce > > -- > 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. -- 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.
