- Original Message -
From: Mike Engelhart <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 17, 1999 11:42 AM
Subject: Re: Long process (Rewrite)
> Correct me if I'm wrong, but this sounds like a complete and utter hack.
I
> realize there are lot
> I think you're missing the point of what people have already told you to do.
> What they have suggested will work.
Actually, I didn't miss the point. In my original message, I noted that my
beans have "request" lifetimes for all my servlets, not "session" lifetimes.
> Servlet B's job now is to
>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 17, 1999 8:46 AM
Subject: Re: Long process (Rewrite)
> > In this way, you can have one JSP page that loads data into the
bean
> > and decides whether to show an error, or "please wait" screen. The
"pl
> In this way, you can have one JSP page that loads data into the bean
> and decides whether to show an error, or "please wait" screen. The "please
> wait" screen would refresh after so long to a new page which would be in the
> same session. Before the first page terminates however, it ca
st 17, 1999 2:47 PM
To: [EMAIL PROTECTED]
Subject: Long process (Rewrite)
Thanks for all the replies, but I don't think I posed my question in enough
detail. While setting refresh headers certainly works for just moving to
another page, my situation is this:
I need to be able to partially proc
o you
would not see the first page until the log process had finished anyway.
Dave
-Original Message-
From: Mike Engelhart [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 17, 1999 2:47 PM
To: [EMAIL PROTECTED]
Subject: Long process (Rewrite)
Thanks for all the replies, but I don'
Thanks for all the replies, but I don't think I posed my question in enough
detail. While setting refresh headers certainly works for just moving to
another page, my situation is this:
I need to be able to partially process the request in a servlet before I can
tell whether or not I can continue
