command to export a binary property / file

[dbu]

like #34 but the other way round: export a file from phpcr into the filesystem. ideally this could even be piped, say phpcr file:export | convert --scale ... | phpcr file:import or something...

[dantleech]

That would be cool. I guess we would allow either a specific property or an nt:file node to be exported (as we could then infer the filename).

I wonder how best to handle the choice of stream of file output. When in the shell, dumping to STDOUT would not be useful. I guess we could either have an optional second argument, or force the user to specify either a filename option or --stdout (or --stream or whatever)

[dbu]

--stdout sounds fine for me. i thought there is a convention of using
- for this but found no reference, and not sure if the console can do
that at all. so its nt:file with inferred name to current folder (or a
path that if exists and is a folder creates the file in there), or an
explicit file name (required when its a property) or stdout.

we should have some allow-override flag as well and not overwrite
existing files by default.