Ok, so I finally merged back my whiteboard into trunk and also fixed a few glitches after the merge.
Now, the ResourceResolver implementation may support feature flags if the Features service is available. Yet the bundle does only have a dynamic and optional dependency on the API. So in setups where the Feature Flags bundle is not installed the ResourceResolver implementation can still be deployed and happily works without feature flag support. I tracked all those changes in SLING-3148 [1] I would think we can now resolve this issue. WDYT ? Regards Felix [1] https://issues.apache.org/jira/browse/SLING-3148 Am 27.01.2014 um 15:24 schrieb Carsten Ziegeler <cziege...@apache.org>: >> >> The global one basically just provides access to the raw request while the >> Sling-embedded one also provides access to the SlingHttpServletRequest as >> well as the request's ResourceResolver. >> >> > Ah right, because you don't have the resolver in the global filter...but > this means that all flags are tested twice if they're active on every > request. > Being able to use feature flags outside of Sling looks nice, but ... to > quote "someone" :) ....yagni for now > > If want to have this two step setup, we should switch to lazy evaluation of > the flags on first access. > > Carsten > -- > Carsten Ziegeler > cziege...@apache.org
