Rapid typing into a text field updated by AJAX can lose data

I'm using this module in a data entry/display module I'm writing, so thank you very much indeed for such a neat development.

I've hit one snag so far. I have a slow cumbersome test server that I'm using. I use a text field in my table, with associated callbacks as described in the documentation, and it all works - if I type into the field, the callback gets called and my code runs to update the database row with the new text. However... if I type very quickly, so that new characters arrive before the previous ajax transaction completes, the newer characters don't make it into the database. (as an example, if I type "aaaaa" very quickly, I get "a" or "aa" in the database). If I type one final character once the spinner has gone back to a green tick, then the data is updated properly as you'd expect.

I imagine this is because the callbacks are asynchronous, and the later keystrokes that arrive while an earlier callback is running don't get registered. This might not have been noticed before on faster servers, but if my application is to work in a potentially laggy environment (e.g. over a slow VPN link) it'll be important to fix this.

My "hacky" idea for fixing this, if it's possible, was to put a delay in somehow so that it waits a couple of seconds after the last keystroke before initiating the ajax call. I don't even know if that's possible as yet though from the javascript point of view. The ideal fix is to somehow register that it's had new data during the initial ajax transaction, and for it to re-sync the data again.

Any thoughts please? :)

Regards

Paul.