Re: Programmatically detecting login or logout events

[MartinOShea <ap...@dsl.pipex.com>]

Chris

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.

Thanks

Martin O'Shea.
-- 
View this message in context: http://www.nabble.com/Programmatically-detecting-login-or-logout-events-tp18685933p18770154.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
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

Re: Programmatically detecting login or logout events

[Christopher Schultz <ch...@christopherschultz.net>]

-----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