|
This question has come up before. Here's the nub of the problem. Typical web client/server interactions are more like a walkie-talkie than a telephone. A request is made by the client, the server responds, the connection is broken. The client then makes a further request at another time, if desired. The server may not (absent subversion of the intended method of operation) institute a transaction such as unilaterally sending a progress indicator to the client. You can understand why this is -- servers could bombard unwilling clients mercilessly. You CAN subvert this if your client is willing to stand for it. In your situation, the client is doubtless willing (at least for this one application). Consequently, set up a timer on the client and request a progress page at whatever interval you think is appropriate. A really frequent interval would be a Bad Thang as it represents a virtually useless load on the server and the infrastructure. Useless in the sense that it's merely patting the techs on the butt to stop their whining.
|