There is also the perspective of the application user. In that context an
"application session" is really a subset of the browser session. This
contrasts with what we've been discussing as "application", or lifespan of
the servlets. An need for an application session is what I believe got us
talking about this in the first place.
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.
The existence of this level also means that invalidating the browser session
will potentially dump application sessions, unless the application sessions
are stored with some other mechanism.
Hopefully that clears up where I was coming from.
Dan
> ----------
> From: Craig R. McClanahan[SMTP:[EMAIL PROTECTED]]
> Reply To: Craig McClanahan
> Sent: Wednesday, March 31, 1999 1:54 PM
> To: [EMAIL PROTECTED]
> Subject: Re: application object
>
> "Kirkdorffer, Daniel" wrote:
>
> > >> Finally, Yes "application" refers to the specific JSP that is being
> > called NOT
> > >> The Application...
> >
> > Right, so it is just like a "global" variable that exists for the
> lifetime
> > of the pagecompiled JSP (which is a servlet). Application is a poor
> choice
> > of words here.
> >
> > Thanks,
> >
> > Dan
> >
>
> Gabriel Wong's statement above (the one with >> in front) is not correct
> for
> the 0.92 reference implementation. This implementation stores and
> accesses
> beans with a lifespan of "application" in the servlet context
> (context.getAttribute() and context.setAttribute()), so they are shared
> across
> all the servlets (and JSP pages) in that context -- not just the
> particular
> servlet or JSP page you reference them from.
>
> This corresponds to the direction the servlet API is headed (a servlet
> context
> being treated essentially as an application), so the choice of
> "application" as
> the term makes a lot more sense when you understand what it is really
> doing.
> Previous comments from Sun engineers on this topic imply that this
> behavior (as
> well as the corresponding behavior for session and page lifespans) will be
> formalized in the 1.0 JSP spec.
>
> Craig McClanahan
>
> ==========================================================================
> =
> 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".
