>If the processing status >is "in progress" Be careful if you expect the "in progress" status change to "done". If an error happens and the status never switches to "done", the session ID will remain forever "in progress" and a second attempt of the same request will be refused by your own application. I use the "done" status immediately in my own applications. Just for info, my own server has plenty of pages where there is a "double click risk", but I have never been able to reproduce the problem by double-clicking the "Submit" button myself. Do both Netscape and MSIE have "doubleclickproof" Submit buttons? Also, I have not yet received a single problem report from my own server due to that problem, although my clientele is entirely computer-illiterate. Anyway, I guess there is absolutely no way to know if receiving two identical requests from the same SessionID would mean or no that the user had double-clicked Submit. I don't think you can rely on the time interval between the two requests, due to network latency and the fact of having the two requests treated by two distinct children. Vic.
