Josh Canfield wrote: > > If Autocomplete isn't want you want then you could implement a > timeout so you only send the data when the user pauses. You can look > inside the scriptaculous code for an example. >
Thanks. I actually have implemented a timeout so it only submits when the user pauses. I've set it to 300ms, so it can cope with a bit of network latency issues, but it isn't a 100% reliable solution. The other spot I use the same approach in is for some calculated fields, they calculate and update as the user types (or when they pause after typing). But still if the first response takes 3 seconds and the second only takes 200ms (which is what my anti-virus is causing to happen!, when I disable it everything works better) then I need something more reliable than a timeout, and it doesn't make sense to make the timeout 4 seconds. Do you know of any libraries or avenues to start working on a token to track that requests / responses are in order?. It is a generic problem so I am hoping there is something out there already. Very similar issue really to when a user hits the back button in a non-ajax environment. Or even if someone hits a submit button twice. Frameworks should have thing built in that are configurable to handle this sort of thing. THanks, Ryan -- View this message in context: http://tapestry.1045711.n5.nabble.com/T5-1-Ajax-requests-and-responses-out-of-order-tp2524956p2531877.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
