Hi Stefan, On Fri, Oct 17, 2014 at 11:56 AM, Stefan Seifert <sseif...@pro-vision.de> wrote: > ... https://cwiki.apache.org/confluence/x/1ATTAg ...
Thanks for this. Looking at your use-cases it feels like your context is always derived from the current resource's position in the content tree, am I correct? If yes that explains why you suggest putting the configuration alongside the content - but we might want to also support configs stored under /conf or somewhere else safe. Quoting Alex K earlier in this thread >> ...configs have a different management lifecycle and ACLs than content ... which can be true but not in your use cases, IIUC - so both options probably make sense. -Bertrand
