Michael Wechner wrote:
Andreas Hartmann wrote:

Hi Lenya devs,

reading the code, it seems like the meta data are not stored
together with the content if you choose an external location.

Is this correct?


meta, data and resources are being saved within the external location.

OK, that's good to know :)

You might want to give it a try and you will see ;-)

I once tried it, but I wasn't sure anymore about the meta data.

But RCML (and I think also versions) are not being saved within this external
location, which needs to be fixed.

Btw, I think meta, sitetree, rcml and rcbak should be separated from the actual data, because these are Lenya specific things and the actual data is customer specific

I wouldn't call it "Lenya specific" or "customer specific". The storage
is in the responsibility of the respective component handling the data,
which can be a default core component or a custom component which
replaces the core component. This applies to all of these data.


If yes, is it intentional? I could imagine that one wants to
store content for example on NFS to be shared by multiple
servers, in this case the meta data should be on the NFS as well,
shouldn't they?

sure, see above


BTW, IMO all stored data (content, users, policies, ...)

users and policies can also be saved external by adapting ac.xconf, but I don't think that the ac stuff should be using the config <content-dir from publication.xconf by default, because one can have different access controllers, but yes a specific implementation could also use it which would make sense to make the configuration simple

OK, IMO the default implementation should use the repository
layer to store access control data to benefit from the transactional
behavior.

-- Andreas

--
Andreas Hartmann
Wyona Inc.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
[EMAIL PROTECTED]                     [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to