As we realize so far, a browser window may send
request A to a server. The server starts thread A
to handle it. Before the thread A returns, the same
window may send request B to the server, therefore
the server creates thread B to handle it.
Assuming thread B finishes earlier than thread A, we
could have the following possibilities:
1) The server waits thread A to finish and send response A
and then send response B. (I do not believe this is the
Tomcat implementation, correct?)
2) The server sends response B back to the browser
window and the browser window displays it and ignores
response A after it.
3) The browser displays response B and then displays
response A.
What I can see is that thread B is the trouble maker. But it
is possible when end users click more than one buttons.
In Swing, such problems are resolved by Single Thread
Model. Should we follow Single Thread Model at
servers? Are there any other practical solutions to it out
there?
Jing
Netspread Carrier
http://www.netspread.com
