Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4894F864.1070005@christopherschultz.net>
Date: Sat, 02 Aug 2008 20:14:28 -0400
From: Christopher Schultz <chris@christopherschultz.net>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Programmatically detecting login or logout events
References: <18685933.post@talk.nabble.com>
 <4891CDE3.8010205@christopherschultz.net> <18770154.post@talk.nabble.com>
In-Reply-To: <18770154.post@talk.nabble.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin,

MartinOShea wrote:
| Thanks for the reply. In the various servlets making up this
application, I
| don't currently have a user object in every request but tend to use
| request.getRemoteUser() where necessary. This also to minimizes
traffic. But
| what you've suggested is good.

You don't necessarily need a user object -- just something that you can
use as a marker in the session to indicate that you have processed the
login. It can be as simple as a key and Boolean.TRUE stuffed in there.
Don't make things more complicated than necessary.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiU+GQACgkQ9CaO5/Lv0PD1VgCgvmVzKNO2g8VrR4JXaj4YEuoS
pNcAnjbtQdLBAIgNxLQmjUie/fw2lrEi
=L9rd
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org