Hello,
We have a website of the following form:
Tier 1: Application server ( which communicates with the database ). Communicates with web server via XML transactions, over sockets.
Tier 2: web server (
Tomcat server, mostly
JSP pages ). The communication over sockets is localized into one
Java class ( which we call ClientSocket ).
Tier 3: web browser
What happens is that if the user clicks "Submit", and then clicks "Submit" again, ClientSocket gets confused. I want to make Tier 3 smart enough to know when Tier 2 is still waiting for data from Tier 1. Right now it is rather simplistic in that it just sets a true/false flag inside the JSP page itself. So it is not particularly accurate, and sometimes the flag gets set to "false" by accident, eventhough it is still being process. Currently, if the flag is true, we popup a message asking them to wait.
I have thought about using AJAX. I have also thought about using the
JSF component validation stuff. I am not experienced with either. What is the best way to make the Tier 3 smart enough to know that Tier 2 is still waiting for data from Tier 1? If I can figure that out, I can decide how to handle the situation.
Thanks.
Tony