Burak Doğruöz wrote:
I don't think that it can be done with an ajax approach. With ajax or not,
concurrent requests for the same action name returns first action's result.
I tried this simple scenario with an action which outputs its query
parameter. I also added a thread.sleep in execute method to gain extra time
to call the same action more than once.
When i triggered the same action with different parameters in 2 separate
browsers, first one redirected to the wait page as expected. At that point i
triggered the second copy. When they both returned from wait page, both
output were first action's parameter.
I think ajax/div approach would show the same behaviour with the above.
If you're using ajax, forget the wait page and redirection paradigm.
One async request maps to one action instance in one thread. There's no
interference or coupling between action instances at all in S2 unless
you introduce the coupling yourself
(or use the exec&wait interceptor).
The "waiting page" would instead be a client-side controlled indicator
displayed while waiting for the async response. It's a common pattern
intended for exactly what you're trying to do when javascript is available.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
