Hi, On Mon, Jun 22, 2009 at 9:16 PM, Carsten Ziegeler<cziege...@apache.org> wrote: > ...I suggest to change the script resolution to use the admin > session....
Sounds good for now, though we might later want to use specific credentials for that. When working with JCR, I miss the unixish execute permission bit, user owner and group owner attributes, and (maybe) setuid bit, we might want to introduce such concepts later. But not right now, no time for that ;-) >... Btw, this would also make caching the script resolution easier as the > current approach requires the caching of the script resolution to be a > per user cache. With the changes from above the cache can be global... Cool. > ...2) Resource events > > We need to implement https://issues.apache.org/jira/browse/SLING-944 and > some extension of this to properly update the cache if scripts are > changed, added removed. As scripts can be coming from any data source > (jcr, file system, bundle, database etc.) we need a generic mechanism here. > For now I think we could start with OSGi events for > - Resource added, removed, changed > - Resource Provider added, removed... Ok, as long as this doesn't lead to duplicating JCR functionality. -Bertrand
