Hi Reinhold. > Concurrent Threads can override each others persistent page properties during rewind
If you mean that observeChange() is not called during rewind, you are incorrect. Rewind is still a render, but the results of the render are discarded. I agree that Tapestry should have taken care of this internally, and I've stated that several times on this list. But the fact is that serializing requests or disabling buttons are the only options available. > But I have a bad feeling about that. Good. ;-) With multi-threading, _some_ kind of serialization is required. Cheers, Nick. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
