I don't know, this is all made up, but...
On 9/15/2010 10:36 AM, Tom Anderson wrote:
1. User is on the order review page and clicks 'confirm'
2. User goes quickly to a 'were processing ur order lol' page, and waits
for it to sponteneously occur that ...
3. User arrives at the order confirmation page
I would have page number 2 switch to "long poll" right now to determine
when page 3 is ready. I other words, you have two URLs:
2a. www.mysite.com/lol_processing
2b. www.mysite.com/process_card?n=1234455667890
Page 2a loads, then tries to load page 2b. When it get a response, then
it loads the confirmation page, possibly using some sort of key returned
by 2b.
This is just:
A. The simplest thing I could think of.
B. Doesn't need to use any thread manipulation. 2b can take as long as
it likes.
C. Doesn't bake any UI rules into the servlets. Each URL is an
independent task. The UI itself takes care of timing/presentation.
D. System testing should be easier as a result.
Again, no special experience, just trying to simplify the interaction.
It is simpler. And it will work in a simple servlet container.