El mar, 05-09-2006 a las 10:31 +0200, Andreas Hartmann escribió:
> Jörn Nettingsmeier wrote:
> > hi everyone!
> > 
> > 
> > looking at thorsten's ac work i realized that we still have hierarchical 
> > "storage" for the policies.
> 
> Do we want to protect URLs, or documents?

The problem that we have ATM is that even the ac is protecting
URL/subtrees it still assumes to have an underlying document. ...or
better the GUI is assuming it since the tab depends on the sitetree.

> For example - if you exchange the document of a sitetree node (=URL),
> should the policy be moved with the document, or stay attached to
> the node?

Good question, I think moving a "URL" you would probably update the ac
as well (as default usecase). Still it would be nice to have a dialog
that will ask whether or not to move.

> 
> > although we have gotten rid of that for the 
> > content after the introduction of uuids, we still need to shuffle 
> > directories around for the ac "repository" whenever a user changes the 
> > sitetree.
> > 
> > what's the plan to get rid of that? would it be feasible to integrate 
> > the url/subtree policies into the sitetree? it would be nice to debug 
> > (everything in one place), and we can lose the horrible directory 
> > structure...
> 
> I wouldn't add specific elements / attributes to the site structure.
> How about site node meta data?
> 

Hmm, that's brings it back to what we have now. That is why I asked to
have something like sitetree-ac.xml where we store the ac in a tree.

wdyt?

salu2

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

-- 
Thorsten Scherler
COO Spain
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