2014-03-21 5:16 GMT-07:00 Justin Edelson <[email protected]>: > Not really, based on my understanding that such an experimental bundle > isn't actually possible (i.e. that sling:feature support can only be > implemented in the Resource Resolver) and would instead be a fork of > the Resource Resolver. >
Well, its probably easier to do in the resource resolver, but nothing prevents us from finding another way if required. I don't see a problem with a fork of the RR for experimental stuff. I still don't think that we have a clear picture of how exactly feature flags in content should be handled. First we decided to always evaluate them, then we found out that this breaks a POST, now they are just handled for GET/HEAD requests. But are we 100% sure that this is the way to go? In addition, the evaluation has a performance impact. Is this acceptable? And then the problems already mentioned in this thread. And we don't have any experience with feature flags in general. Therefore my suggestion is still, let's remove it for now, do a release (of the RR and the feature flags bundle) and then revisit this and do it right. Regards Carsten
