Hi As I repeatedly said, I think the Feature Flags support should be implemented without the ResourceAccessGate mechanism because it is not an access control thing but a purely operational visibility thing. Also as opposed to access control, feature flag enabled can and should be controllable by a consumer of the API; for example by passing a request parameter on the request.
Based on the existing code, I have created a prototype in my whiteboard at [1]: * On a per-resource level feature flags are set as sling:feature properties of type String or String[] * Flags are checked during resource resolution in the ProviderHandler.getReadableResource method * Feature services can implement ResourceDecorator such that they can decorate a resource in case their feature is enabled. I also provided diffs in the feature-flags and resourceresolver projects to be able to see, what has been changed. WDYT ? Regards Felix [1] http://svn.apache.org/repos/asf/sling/whiteboard/fmeschbe/featureflags
