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). > > Regards, > > -- Rodney 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. -jon -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
