Re: [featureflags] Readding sling:features to resourceResolver

2014-06-17 Thread Carsten Ziegeler
I still think an utility method is the best/easiest approach. What is the real problem with doing that? Adding feature flag to the resource resolver requires to check a property for each and every resource access - and I don't see a good reason why this burden should be added for a use case which

Re: [featureflags] Readding sling:features to resourceResolver

2014-06-16 Thread Dominik Süß
of featureflags. Best regards mike -Original Message- From: Dominik Süß [mailto:dominik.su...@gmail.com] Sent: Tuesday, June 10, 2014 2:53 PM To: dev Subject: [featureflags] Readding sling:features to resourceResolver Hi everyone, although I know this touches an area

Re: [featureflags] Readding sling:features to resourceResolver

2014-06-16 Thread Bertrand Delacretaz
Hi, On Fri, Jun 13, 2014 at 12:10 AM, Carsten Ziegeler cziege...@apache.org wrote: ...I think we should go back to talk about use cases I agree, and keeping the list at https://cwiki.apache.org/confluence/display/SLING/Sling+Feature+Flags+support up to date might be a good starting point.

Re: [featureflags] Readding sling:features to resourceResolver

2014-06-16 Thread Bertrand Delacretaz
Hi, On Tue, Jun 10, 2014 at 2:53 PM, Dominik Süß dominik.su...@gmail.com wrote: -... Currently writing frontend that needs to adapt to featureflags requires adding custom code to check and filter the ui to be rendered. This leads to a lot of boilerplate code written over and over again with

Re: [featureflags] Readding sling:features to resourceResolver

2014-06-16 Thread Dominik Süß
Hi Betrand, I fear it is not as easy since this mandates rendering engines to be able to perform that filtering (in other words - to be able to skip rendering based on the feature flag) or we would require developers to utilize filters which are way more intrusive then a Resource Access Gate and

Re: [featureflags] Readding sling:features to resourceResolver

2014-06-16 Thread Bertrand Delacretaz
Hi Dominik, On Mon, Jun 16, 2014 at 1:55 PM, Dominik Süß dominik.su...@gmail.com wrote: ...I fear it is not as easy since this mandates rendering engines to be able to perform that filtering (in other words - to be able to skip rendering based on the feature flag)... so IIUC you're looking at

Re: [featureflags] Readding sling:features to resourceResolver

2014-06-16 Thread Dominik Süß
Hi Bertrand, I'm not really about altering resource rendering but enable disable resources for rendering, so I probably wouldn't decorate the scripts and servlets but the resources that define those resourceTypes. This is what we all have done a lot when hiding away frontend for endusers (at

RE: [featureflags] Readding sling:features to resourceResolver

2014-06-12 Thread Mike Müller
the solution could really be to wrap the ResourceAccessGates for the functionality of featureflags. Best regards mike -Original Message- From: Dominik Süß [mailto:dominik.su...@gmail.com] Sent: Tuesday, June 10, 2014 2:53 PM To: dev Subject: [featureflags] Readding sling:features

Re: [featureflags] Readding sling:features to resourceResolver

2014-06-12 Thread Carsten Ziegeler
: [featureflags] Readding sling:features to resourceResolver Hi everyone, although I know this touches an area with a lot of emotions involved I wanted to reopen the discussion around Featureflags support for the resourceresolver. The last thing that happend was removing it for a release due

[featureflags] Readding sling:features to resourceResolver

2014-06-10 Thread Dominik Süß
Hi everyone, although I know this touches an area with a lot of emotions involved I wanted to reopen the discussion around Featureflags support for the resourceresolver. The last thing that happend was removing it for a release due to potential confusion and subtle issues. See