On 6/23/06, Mark Stang <[EMAIL PROTECTED]> wrote:
Actually, I think it was just a listener method. There wasn't a deadlock, maybe it should have been sync'd. However, the question came up about listeners in general. And I think the real question is shouldn't listeners and submits by design, only allow one click of each? Should Tapestry by default disable links and buttons until it returns?
I believe that it would be better if tapestry would provide mecanisms to synchronize requests from the same user and queue them. This way two requests from the same user wouln't be executed simultaneously. Thanks, Henri.
