Far away to understand your code I would recommend to disable all buttons (A,B,...) if the user presses button A. In the RPCs onSucces/ onError methods reactivate all buttons. To avoid that all buttons become disabled for ever if the server doesn't answer, implement a timeout with a timer. Start this timer simultaneous with the 'A' RPC call. GWT buttons can change their appearance in the 'disabled' state with CSS. So the user can see, that's not possible to press button B or button A twice. Although I think users are familiar with the asynchronous behavior of the internet. Another approach would be that thread B stops thread A on the server if it is still running. I've done this in connection with table paging to stop a cache filling thread. And it was a nightmare. But sometimes you have to stop time-consuming threads on the server if the user decides at once to call up some other information. Holger
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
