On Sun, 26 Jan 2003, Jon Scott Stevens wrote: > on 2003/1/26 8:07 PM, "Rodney Schneider" <[EMAIL PROTECTED]> > wrote: > > > On Fri, 24 Jan 2003 19:18, you wrote: > >> Hi to the Community, > >> > >> Has anyone ever thought of implementing the turbine security service > >> in a different way? Why not use the Java Servlet Filtering API this > >> way one could easily implement different SessionValidators, etc... > >> > >> Using the FilterChain and a clean Chain of Rsponsibilty Pattern would > >> make changes more than easy. One could implement different > >> Authorization Filters, different Authentication Filters, etc. Just > >> Plug them in and they will work. > > > > A similar concept has already been implemented in the Turbine 3 > > pipeline, which consists of a sequence of valves (very similar to a > > filterchain which is a sequence of filters). > > Note: Turbine has been around far longer than Servlet API filters. So, that > is why Turbine really doesn't take advantage of them. The other reason is > that the API for filters kind of sucks. Sigh, of course I tried to convince > Danny to do the Servlet API filters differently and he didn't listen to me > at all.
Some day I'd like to look at providing Valve wrappers for Servlet API filters. As you can do more with a Valve than you can with a Filter, this may be feasible, and would allow those who have already invested in developing Filters to easily plug them into Turbine's Pipeline architecture. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
