I have never looked at the filtering API... Sounds like a reasonable idea though. You might want to post this to the turbine-dev list to get a discussion going.
> -----Original Message----- > From: J�rgen Hoffmann [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 23, 2003 4:32 AM > To: [EMAIL PROTECTED] > Subject: Servlet Filtering API > > > 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... > > +---------+ +----------------+ +--------------+ +------+ > +-----------------+ > | Req,Res |--| Authenticated? |--| Authorized ? |--| etc. |--| Turbine > Servlet | > +---------+ +----------------+ +--------------+ +------+ > +-----------------+ > > 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. > > Am I thinking the wrong way? > > Kind regards > > J�rgen Hoffmann > > > -- > To unsubscribe, e-mail: > <mailto:turbine-user-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
