On 10/17/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > ...So for now, I personally tend to go with filters except where something > is really required for Sling core to work. There we could use an > explicit service instead....
I think that's a very good criteria: if something's always required by Sling, make it a service, *and* make sure its interface exists in the api package, to make it well visible. I agree that authentication might be better handled by a filter, as it's a common way of doing that. -Bertrand
