tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard W. Smith, Jr." <>
Subject Re: getting the request that created the session
Date Mon, 29 Apr 2013 19:22:42 GMT
On Mon, Apr 29, 2013 at 12:55 PM, Leon Rosenberg

> Whether you want to have multiple filters or not is a decision based on
> your coding guidelines, architectural principles and what not.
> Since you are the only user of your filters, it's free to you to use as
> many (or few) filter as possible. Personally I would like to separate by
> concerns and have multiple filters, because it makes it easier to use,
> maintain and test. But this is personal opinion.
> However, in my case, I am developing a library that is used by others in
> their projects ( It comes already with 8
> filters (
> )
> and this is a lot. Of course the end user (developer) only chooses the
> filters he needs, and not everyone needs everything. However, since its a
> lib, you don't want it to show up in your stack traces every request, you'd
> rather forget, that you have it at all. Therefore I'm trying to choose a
> less visible approach ;-) Also it's easier to add one listener to web.xml
> as to add a listener AND a filter. And I need the listener, to know when
> sessions expire anyway ;-)
> But again, your situation is obviously different from mine ;-) But if you
> want to count sessions and all the other funny stuff, give moskito a
> chance:
Agreed-and-understood on all points. I am definitely interested in a better
approach to managing/monitoring sessions in my web app (that is why i find
this thread interesting), but ATM, my current session-management/monitoring
implementation meets /my/ requirements.

If/when I get a moment (or some bandwidth), I may take a look at your what
you have developed. Thanks.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message