On Sun, Jun 26, 2011 at 2:13 PM, Les Hazlewood <[email protected]> wrote: > Also, Kalle, why do you think this might be a better approach than > using request attributes to reflect path/request-specific > configuration? I'm curious as to the thought process as this diverges > from the 'traditional' servlet model.
Using request attributes would have other interesting benefits, like sharing same configuration between different filters, but to answer your question: it's better because it'd be simpler to implement (less lines of code) and it would perform better. I think it's a typical case for trading memory for better performance. Obviously, it's not like other suggested implementations would perform drastically worse, but on the hand fairly limited number of multiple filter instances don't consume that much more memory either. So together with the simplified implementation, it seems like a reasonable win without major drawbacks. Kalle
