t: Thursday, 16 November 2000 3:01 PM
To: Orion-Interest
Subject: RE: Client hits STOP button..is there a way to detect this
before sending a response?
Thats a good approach to take for things like a "list" of items, such as a
search engine or a list of rows from a table. But what abou
On Wed, 15 Nov 2000, Kevin Duffey wrote:
> So in code it might look something like:
>
>
> {
> SomeSession ss = new SomeSession();
> SomeBean bean = getBean(); // gets the javabean used by jsp page
>
> Date date = new Date();
> ss.setDate(date);
> bean.setDate(date);
>
> ss.doLogi
Thats a good approach to take for things like a "list" of items, such as a
search engine or a list of rows from a table. But what about when your
building up a single transaction, and you need to keep the state of several
pages across requests? While there is even less of a chance of what I am
ask
Hi again,
Actually..I hashed out your first idea with two other guys and it seems like
it should work. Let me see if I got this straight.
1) When the action class is called..create a timestamp.
2) Create the stateless session class.
3) Get the javabean associated with the series of pages (sessio
On Wed, 15 Nov 2000, Duffey, Kevin wrote:
> Thanks for the reply..
>
> Your idea has some merit..the only problem is, we have so many different
> searches and profile updates that could be happening..I would need to keep
> track of each of those separately.
>
> Here is what I had in mind if t
the variables could get screwed up. I don't want to use
the Singleton model though.
> -Original Message-
> From: Hani Suleiman [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 15, 2000 3:49 PM
> To: Orion-Interest
> Subject: Re: Client hits STOP button..is
Quick answer - i dont know how to do an 'early detection' of the user
pressing the stop button. I dont think its possibly - at least I dont think
there is a non-super-difficult way of doing it.
I think you may need to do more than just put your results bean in the
session when providing a means t
Here's another approach.
Put a timestamp in your session to denote when a search request was
started, and have the searcher object track this timestamp too. When you
get the results back, check that the timestamps match before populating
your bean. If another search had happened in the meantime,
"Duffey, Kevin" wrote:
>
> So here is the problem. If a user submits a form (say..to search for all
> clients) and lets say that search will take two minutes. 10 seconds later,
> the client sees he/she made a mistake on what they were searching for. As if
> often the case..they hit STOP on the
