This isn't a question. This is a description of a project... do you have a question about this project?

Update: Oh. Ok... I suppose that line about the back button implies a question of sorts.

One way to get around this sort of thing is to have a sequence number submitted with each request. If the CGI gets the a number less than the one it is expecting, it doesn't modify the user's state. This doesn't work for all situations. It won't work if the user wants to go back to the last form change something and resubmit, for instance. For that functionality, you could provide your own way to get back and forth between form and warn the user when they navigate via other methods. A savvy user might also easily foil this if they tried. You should consider the implications of that possibility.

-sauoq
"My two cents aren't worth a dime.";