Return-Path: 
 <tomcat-user-return-55363-qmlist-jakarta-archive-tomcat-user=nagoya.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org
Received: (qmail 42962 invoked from network); 27 Feb 2003 15:10:54 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 27 Feb 2003 15:10:54 -0000
Received: (qmail 3727 invoked by uid 97); 27 Feb 2003 15:12:31 -0000
Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org
Received: (qmail 3720 invoked from network); 27 Feb 2003 15:12:30 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by nagoya.betaversion.org with SMTP; 27 Feb 2003 15:12:30 -0000
Received: (qmail 41051 invoked by uid 500); 27 Feb 2003 15:10:29 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-user-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-user-help@jakarta.apache.org>
List-Post: <mailto:tomcat-user@jakarta.apache.org>
List-Id: "Tomcat Users List" <tomcat-user.jakarta.apache.org>
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 40998 invoked from network); 27 Feb 2003 15:10:28 -0000
Received: from unknown (HELO pandc2501.panamericano.com.br) (200.184.29.3)
  by daedalus.apache.org with SMTP; 27 Feb 2003 15:10:28 -0000
Received: by pandc2501.panamericano.com.br with Internet Mail Service
 (5.5.2653.19)
	id <FX4F57ZZ>; Thu, 27 Feb 2003 12:10:17 -0300
Message-ID: 
 <4EFE7B26CE175F4B9653BD51D199CCFC0154DD5B@panms2505a.panamericano.com.br>
From: Edson Alves Pereira <eapereira@panamericano.com.br>
To: 'Tomcat Users List' <tomcat-user@jakarta.apache.org>
Subject: RE: Sharing session info between Tomcat and IIS
Date: Thu, 27 Feb 2003 12:02:23 -0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2DE71.3BD37620"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

------_=_NextPart_001_01C2DE71.3BD37620
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

	Try to use cookies, if you between ASP and JSP.to share information
or you could the the URL like http://127.0.0.1/blah.jsp?login=3Dedson

> ----------
> De: 	Schleimer, Ben[SMTP:bensch128@yahoo.com]
> Responder: 	Tomcat Users List
> Enviada: 	quinta-feira, 27 de fevereiro de 2003 11:19
> Para: 	Tomcat Users List
> Assunto: 	Sharing session info between Tomcat and IIS
>=20
> Hi,
>=20
>   I am working on a project which must  securely
> Timeout the user for security purposes. Unfortunately,
> all of the login/logout code has been written (not by
> me) in ASP. I really want to use Servlets for the
> project instead of ASP. I was thinking of storing the
> user's last access time in the backend DB and updating
> it everytime a user makes a request to Tomcat. But
> this requires a DB lookup every request. Is there a
> more direct way to communicate session info between
> IIS and Tomcat?
>=20
> Thanks,
> Ben
>=20
> --- Greg Speechley <greg@learnedsolutions.com> wrote:
> > Hi Yoav,
> >=20
> > I was wondering why using sessions is unreliable for
> > tracking users who are
> > logged in, getting last accessed time, etc? I would
> > have thought that
> > storing all the current sessions in a Vector (or
> > some other data structure)
> > with a User object (storing all their relevant info)
> > bound to each session
> > would work well. What alternative would you suggest
> > because the situation
> > described by R.C.Nougain sounds very similar to what
> > we have where I work.
> >=20
> > Cheers
> > Greg Speechley
> >=20
> > -----Original Message-----
> > From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]
> > Sent: Wednesday, 26 February 2003 12:46 AM
> > To: Tomcat Users List
> > Subject: RE: Tomcat 4.1.18 session objects
> >=20
> >=20
> >=20
> > Howdy,
> >=20
> > >Where can I find the changes list from Tomcat 4.0.x
> > to Tomcat 4.1.x.
> >=20
> > Download any release of tomcat.  Explode the
> > distribution and you'll see a
> > bunch of release notes files, one for each labeled
> > release, detailing what's
> > new in that release.
> >=20
> > >| For each user session I store the reference| to
> > the session in a Vector
> > >so that I
> > >| can tell what users are logged-in,
> > last-accessed-time etc. It was working
> > >fine
> > >| in Tomcat 4.0.4. But in Tomcat4.1.18 (perhaps due
> > to new specifications)
> > >session
> > >| objects are pooled (StandardSessionFactory) and
> > hence the references I
> > >| am storing in the Vector become useless across
> > the jsp page calls. I have
> > >a
> > >| thread that uses this Vector to clean up the
> > users that are timedout but
> > >since
> > >| the session refs in my Vector are useless I can
> > do nothing. Instead of
> > >| storing the refs if I store Session IDs then can
> > I get ref to a session
> > >from
> > >| JSP Server so that I can get the attributes I
> > have set in it. Please
> > >comment.
> >=20
> > Since you only asked for comments... There is no new
> > specification regarding
> > http servlet sessions from tomcat 4.0 to 4.1.  It's
> > still the servlet spec
> > v2.3.
> >=20
> > Your design is vulnerable to any changes in the
> > container session fa=E7ade
> > implementation.  Note that the container is not
> > required to provide you with
> > a session list per se.
> >=20
> > I don't think using sessions to track who's logged
> > in and last-access-time
> > for resources is reliable.  But if you want to do it
> > that way, write an
> > HttpSessionListener.  It was created for these sort
> > of session tracking
> > things.  Move your vector into that listener.  Add a
> > reference each time a
> > session is created, remove it when a session is
> > destroyed.  Add whatever
> > other functionality you need to the listener.
> >=20
> > Yoav Shapira
> > Millennium ChemInformatics
> >=20
> >=20
> >=20
> > This e-mail, including any attachments, is a
> > confidential business
> > communication, and may contain information that is
> > confidential, proprietary
> > and/or privileged.  This e-mail is intended only for
> > the individual(s) to
> > whom it is addressed, and may not be saved, copied,
> > printed, disclosed or
> > used by anyone else.  If you are not the(an)
> > intended recipient, please
> > immediately delete this e-mail from your computer
> > system and notify the
> > sender.  Thank you.
> >=20
> >=20
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> > tomcat-user-help@jakarta.apache.org
> >=20
> >=20
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> > tomcat-user-help@jakarta.apache.org
> >=20
>=20
>=20
> =3D=3D=3D=3D=3D
> "The competent programmer is fully aware of the strictly limited size =
of
> his own skull; therefore he approaches the programming task in full
> humility, and among other things he avoids clever tricks like the =
plague"
> - Edsger Dijkstra
>=20
> http://snow.prohosting.com/bensch
>=20
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Tax Center - forms, calculators, tips, more
> http://taxes.yahoo.com/
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>=20

------_=_NextPart_001_01C2DE71.3BD37620--