I agree with Bertrand. Generally, I'm in favor of supporting the Accept header.
However coding an arbitrary logic into Sling Engine (or some other core bundle) does not sound good to me. The benefits of a pluggable solution would be - preservation of modularity and - the implementation of some "special" logic could live in a "contrib" bundle, where it's easier to drop support, if the idea turns out to be not so good. - other headers, e.g. Accept-Language, could also be easily supported. Regards Julian On Mon, Apr 7, 2014 at 10:13 AM, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > On Mon, Apr 7, 2014 at 9:58 AM, Felix Meschberger <fmesc...@adobe.com> wrote: >> ...I would prefer to not go over board, at least not initially, and keep it >> simple and covering simple use cases.... > > I like simple but what I object to is burning this into the Sling core > - what you suggest is based on somewhat arbitrary rules (single > content-type etc) which I don't feel good burning into the core. An > extension point for setting selectors + extensions is not rocket > science. > > -Bertrand
