I can’t quite adapt your analogy to filling in a form. So Bob is the server and Alice is the user? What are the arrows? Also in your Analogy, Bob shouldn’t count the arrows, instead he should count the time while no arrows are in sight (as he might start sunbathing a bit to soon and get shoot by a late arrow)
If you look into the thread that I have posted, you see the original problem specification:
The Form contains a “username”, a “password” and a “passwordRepeat” field.
- The server should check if the username is free
- The server should check if the two passwords are the same and if the password is contained in the list of unsave passwords
To do so the following should hold true:
- The server will wait until the user has stopped typing within 500ms.
- If the user starts typing again, the server request should be aborted
- Switching between input fields should be considered
- Switching to one input and back to the other within the 500ms should not trigger an abort Event
- No data may be lost during switching