Hi,

"- Your user submits a form to an action that takes a long time,
  but gets impatient, presses STOP, and submits the form again.
  You now have two simultaneous requests to deal with."

But is there any specific set of methods to deal with the 
Multiple requests simultaneously from a user ? 

1 . If the second request needs to be killed and only the 
First request should be processed
2 . All the simultaneous requests should get processed .. 

Thanks.

Mahesh

-----Original Message-----
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, July 18, 2002 12:29 AM
To: Struts Users Mailing List; [EMAIL PROTECTED]
Subject: RE: Re[2]: Pre-Populating Form




On Wed, 17 Jul 2002, Joseph Barefoot wrote:

> > [snip]
> > Session attributes, on the other hand, can be accessed by multiple 
> > threads at the same time.  You don't have to synchronize the servlet

> > API calls like session.getAttribute() or session.setAttribute() -- 
> > the container takes care of making that work correctly.  Within your

> > session beans, though, you need to be aware that multiple threads 
> > can be calling your methods at the same time.
>
> I must confess, I'm a tad confused by this bit.  I was under the 
> impression that there was always a 1-to-1 relationship between servlet

> threads and HttpSession objects -- each thread is associated with an 
> HttpSession object, and only that thread can access the object.  If 
> this is not correct, then what are the additional threads, and in what

> scenario would they be accessing the same session object?
>

Here are three easy ways to have multiple requests (and therefore
multiple threads) accessing the same session at the same time:

- Your application uses frames.  Most browsers will fire off
  simultaneous requests for each frame, which shows up at the
  server as multiple requests on the same session.

- Your application uses <img src="..."> tags to dispay images,
  and those images are in the same webapp.  Again, the browser
  will fire off multiple requests simultaneously.

- Your user submits a form to an action that takes a long time,
  but gets impatient, presses STOP, and submits the form again.
  You now have two simultaneous requests to deal with.

Craig



--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

**************************Disclaimer************************************************** 
   
 
 Information contained in this E-MAIL being proprietary to Wipro Limited is 
'privileged' 
and 'confidential' and intended for use only by the individual or entity to which it 
is 
addressed. You are notified that any use, copying or dissemination of the information 
contained in the E-MAIL in any manner whatsoever is strictly prohibited.

****************************************************************************************




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to