Wolfgang,
> BTW: Jackrabbit's default storage -is- the filesystem. Question to
> those
> who have experimented with it thus far: how does it do this, e.g. one
> big file, or one file per "item", or one per "node" and one per
> "property", ... ? I suppose we probably should not rely on that anyway
> (e.g. for automated svn functionality), but I am still curious :)
The good news is: It is not one big file. I wouldn't actually consider
this "filesystem" then but rather "binary". This would be probably what
you get when using the BerkeleyDB backend that I thought I read
something about.
You cannot tell exactly if this is one file per node and one file per
property, but what I can tell for sure:
In the workspaces/data folder of a filesystem repository you will find a
lot of folders with names in hex values that contain other folders with
names in hex values which at some point contain XML files with properties.
In other words: Folders and filenames are entirely unrelated to the
outside view of the repository, which in my opinion renders them useless
for any other purpose but reading and writing the content through
Jackrabbit. (I guess that was the question behind your question.)
Don't forget the basic idea of UUID in JCR. JCR is *not primarily* a
tree structure with folders and files. You can model it that way if you
want, but you can also build entirely different systems of reference. I
think (haven't tried) you can even have parallel systems of referencing
the same content.
Hope this helps.
Regards,
Torsten
J. Wolfgang Kaltz schrieb:
Andreas Hartmann wrote:
Hi Lenya devs,
we have to come to a decision about the repository question.
People stated their opinions, it looks like there are two
general directions.
If you think it's too early for a vote, please request cancelling.
Vote:
(a) Lenya should focus on JCR only. It is OK to implement core
functionality which absolutely relies on JCR features.
+1
Assuming this decision is neutral regarding the question "will Lenya be
used for Apache doco", I'm also
+1
BTW: Jackrabbit's default storage -is- the filesystem. Question to those
who have experimented with it thus far: how does it do this, e.g. one
big file, or one file per "item", or one per "node" and one per
"property", ... ? I suppose we probably should not rely on that anyway
(e.g. for automated svn functionality), but I am still curious :)
--
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
