If it weren't for the users, we'd have a decent site
--#--
Great! It worked, didn't it? The only problem is, it 
doesn't really <i>stop</i> anyone from banging on the 
button. Well, it's a step in the right direction, and I 
know from experience that it'll cut way down on your multiple 
submissions.<br>
<br>
But it won't eliminate them. The only way to do that is to 
take away the user's damn button.<br>
<br>
How? Have your CGI <i>immediately</i> put up a "Processing ..."
page -- fully replacing the page with the form ... and the button. 
But can a CGI program really do that? Put up a page and continue 
processing? <br>
<br>
No, not the way HTTP works these days. Netscape 
developed a technique called "non-parsed headers" or "server push" 
that works quite well with Netscape browsers. The only problem is, 
it's not a standard, and nobody else (including Microsoft IE) 
supports it.<br>
<br>
So we're going to have to get creative. There is a way to do 
this within the HTTP and CGI standards. To find out, read on.
<br>