hi *!
while i'm preparing a patch to change usecase policies to
deny-by-default, it occured to me that we need to modularize default
usecase policies...
how hard will it be to implement the following:
* every module that contains usecases must also contain a
config/ac/usecase-policies.xml
* when a usecase must be authorized, the UsecaseAuthorizer first looks
in <pub>/config/ac/usecase-policies.xml, then in the parent pub, then in
the parent parent, ..., then in the module.
this looks somewhat similar to fallback, but fallback is per-file,
whereas in this case we would need a per-element fallback, similar to
i18n catalog merging.
(in the future, i would love to see per-element fallback anyway, but
getting the overriding semantics right in every case is going to be a
can of worms...)
wdyt?
jörn
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: [EMAIL PROTECTED], Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
