Hi all, Currently, we love using filtering in both Sling and microsling: Every part of request processing is implemented using a filter. This was not always the case: In the days when Sling was still private, there was no filtering at all.
Probably we must come to a mix of both: There are some tasks, which have to be executed all the times and there are some tasks which may or may not be executed. Examples of the former are authentication, proper error handling, resource resolution and servlet/script resolution. Examples of the latter are locale resolution, default setting of the response content type etc. So, for microsling, I propose to not implement resource resolution as a filter, in fact leaving default response content type setting the only filtering task (currently). For Sling I propose to not implement filtering for authentication (replace AuthenticationFilter by a service called directly), errorhandler (replace ErrorHandlerFilter), contentresolution (replace ContentResolverFilter) and component resolution (replace ComponentResolver). These tasks are always executed in the listed order by the Sling request processor. After the component is resolved the registered filters are called and finally the component itself is called. WDYT ? Regards Felix
