Thanks! It seems to be unanimous then, that for the purposes I need,
the listener is the way to go. That was my gut feel as well, but I
don't know enough of the internals of session handling to know why it
would be that way.
GB Developer wrote:
Well let's just think about that for a second.
Filter:
a filter is called each and every time you make a web request. So even if
the filter is highly efficient, if you make 1000 requests in a session, you
(that is, the container) will invoke the filter's doFilter method 1000
times.
Listener:
A session is created exactly once and destroyed exactly once.
-----Original Message-----
From: David Kerber [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 09, 2006 12:16 PM
To: Tomcat Users List
Subject: Re: Logging session timeouts
I still have a question about performance: any idea which of these
methods (filter or listener) will use less cpu time when
handling 50 to
100 simultaneous users, each logged in with their own ID and session?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
