Understood and Agreed...
"Kirkdorffer, Daniel" wrote:
> Well I'm talking about web applications that one has to log into
> (userid/password), or otherwise identify oneself to. What we're interested
> in then is maintaining objects for the duration of the login to the web
> application. Perhaps the user uses a number of JSP systems, then we want to
> ensure the web application objects do not conflict with another's web
> application objects. Thus the idea of an application space.
>
> I like to work with multiple browser windows open at one time. I assume I'm
> not alone in that. We're developing web apps for people that might use more
> than one of them concurrently, in different browser windows. In doing so
> they've established one HttpSession object (as long as they are only using
> one browser type - i.e. all Netscape for instance). Should one web app
> invalidate the session object it would destroy all the objects tied to it,
> and since we've tied our web application Hashtables to it, it would destroy
> all of those too. Thus we remove the web app Hashtables from the session,
> rather than invalidating it, letting the session timeout or end when all the
> browser windows are closed.
>
> Does that help?
>
> Dan
>
> > ----------
> > From: Gabriel Wong[SMTP:[EMAIL PROTECTED]]
> > Reply To: Gabriel Wong
> > Sent: Wednesday, March 31, 1999 3:12 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: application object
> >
> > "Kirkdorffer, Daniel" wrote:
> >
> > > An application session has to be separately managed. Where a session
> > object
> > > lasts the life of the browser (or until invalidated), an application
> > object
> > > lasts the life of a login and logout of the application. In this case
> > using
> > > a scope of "application" is NOT what the doctor ordered.
> >
> > OK I guess its your turn to confuse me - What do you mean by login and
> > logout of
> > the application and also clarify what you mean in the block below ...
> >
> > > invalidating the browser session
> > > will potentially dump application sessions, unless the application
> > sessions
> > > are stored with some other mechanism.
> >
> > ==========================================================================
> > =
> > To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> > body
> > of the message "signoff JSP-INTEREST". For general help, send email to
> > [EMAIL PROTECTED] and include in the body of the message "help".
> >
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
