You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Jürgen Hoffmann <jh...@byteaction.de> on 2003/01/23 11:31:49 UTC

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:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>