OneClick revisited
I've finally gotten around to updating my OneClick control to make it work in applications where pages are served in sequence.
The way OneClick works is by storing a token in a hidden field in the form. If the user posts twice, the token has been logged by the first post, and the OneClick.IsValid property will be false.
Unfortunately, in the old version of OneClick, the form post tracking token was removed when the page was done processing. But this was the wrong thing to do because when pages are served in sequence, the the second, invalid, post was deemed valid because the token had been removed by the first post. Oops :)
Anyway, if anybody using OneClick still has problems with it, let me know.