> > Sure. Use custom solutions, like the one Igor suggested. > > > I think I understand -- we can use exactly the same solution to the form > re-submit problem in the case of [a back-button navigation followed by a > form re-post] to solve the double-submit problem in the case of [a page > refresh after a form post when ONE_PASS_RENDER is being used]. > > In both cases, if we subclass Form and hold state to track whether the form > has already been submitted once before, we can handle the problem the way > Igor suggested previously. Is that correct?
Yep, that sounds like a good option. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
