This could be found in the mail's header:
list-unsubscribe: <mailto:[EMAIL PROTECTED]>
-----Message d'origine-----
De : Jockel, Jeff [mailto:[EMAIL PROTECTED]]
Envoyé : mardi 7 août 2001 14:11
À : [EMAIL PROTECTED]
Objet : PLEASE UNSUBSCRIBE ME
-----Original Message-----
From: Beth Kelly [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 06, 2001 6:19 PM
To: [EMAIL PROTECTED]
Subject: Re: JDBC Realms
Actually, I see why you would not want the passwords in memory.
Kyle Wayne Kelly
(504)391-3985
http://www.cs.uno.edu/~kkelly
----- Original Message -----
From: "Michael Wentzel" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, August 06, 2001 12:13 PM
Subject: RE: JDBC Realms
> > > Advantage: You don't lose existing session data
> > > Disadv : You're not actually re-authenticating
> > (not really authenticating, you lost me)
>
> After looking at some code I figured something out...
> I was thinking about this architecture wrong. Kyle was
> right just using:
>
> session.setAttribute("j_password", sPassword);
>
> will provide a hook for password changes.
>
>
> ---
> Michael Wentzel
> Software Developer
> Software As We Think - http://www.aswethink.com
>
