This is an old revision of the document!

8/7/12 - I was able to implement my idea successfully, and while I still want to extensively test the website once its on the server, I think everything is working correctly now based on all the tests I've run. Basically, I made it so that the client always forwards what it thinks the current commit number is and that number is compared to what is listed in the server. Normally, this is the same, but if the user goes back and resubmits, the old cached number is different from the server number which was updated in the last submit. This way the survey cannot submit the answers to a question in the wrong slot.