Leafless trees are the great unwashed mass of humanity, who are blindly focused on living rather than great ideological debates. Like all people who haven’t seen the light they have to pass through a period of capitalism (summer) before they realize that it is folly. Then they let their true colours shine (autumn). Then their masters get greedy and start repressing them (Winter). Then the whole cycle starts over again.
Keith
“I’m tired of being an object of ridicule. I wanna be a figure of fear, respect, and SEX!”
-Radar O’Reilly
I’m moving this thread up since I’ve noticed an unusual number of multiposts considering the board hasn’t been crashing. I’d like to know:
-
Are new posts not showing up, so you repost and get a multipost? (in which case, trust the CGI! but I’ll mention it to the techs)
-
Is the screen timing out or going slow, so you hit submit a few more times? (in which case, trust the CGI! I don’t know if “going slow” is fixable.)
-
Are you only hitting submit once but you still get multiposts? (In which case, I should report the bug to the techs.)
Let me know what’s going on here. I won’t flame you (this time… 
) if you tell me you hit submit more than once, but I’d like to know if this is a bug or just people getting impatient.
I did it. Guilty as charged for not trusting the CGI. As a newbie, I resubmitted when I got timeout errors and my post didn’t show up in a second window. Now I just cut and paste the text into notepad adn save it on the desktop. If it doesn’t show up eventually I know I still have it.
Twice though, while still typing away at a message, all of a sudden my half finished post (in mid sentence no less!) just submitted itself. I have no idea how or why either. I haven’t seen any posts from others like this either, so it is something I did somehow. (Win98, IE5.0 for anyone else who has had this happen and can enlighten me.)
The problem with ‘trusting the CGI’ is that the CGI is not trustworthy. HTTP connections can fail for lots of reasons without the CGI script firing.
In my case, I double-posted because my first post generated an error from MY proxy server that the page could not be loaded. Now, that could happen either if your CGI script did not respond in time, or if my proxy server timed out, in which case you never got the message at all. So I fired up another browser instance and checked the page, and my message wasn’t there. So I submitted it again. Later in the day, there were two copies.
CGI is a slow technology because it is out-of-process, but even so, some of these delays are pretty bad. It shouldn’t take a CGI module 2 minutes to respond after it receives a posting. You might want to look at your server configurations to make sure they are all correct. I don’t know how the SDMB is set up, but I’d look into increasing the available RAM and using a faster disk subsystem.
See, that’s why I say “trust the CGI”; when you don’t you get multiposts, as I’ve been saying. 
The people who have hit submit and not had a post go through are very very rare, as far as I can tell. I realize it’s annoying to not see your post and wonder if it went through for a while, but it takes me a decent amount of time to clean multiposts up. Ed and the techs do have various things planned that should reduce any delay problems (if you’d like to post your ideas for improving the speed, ATMB would be a good place), but in the meantime please be patient and not so quick to post again. It makes the threads cleaner and my job easier.
Isn’t this something that could be fixed in the CGI itself? Why not compare the text in a post to the previous post from that particular member, and if it’s identical, toss it?
Version 2.0, right?
Ooh, cool idea. I’ll ask the tech guys, although I’m afraid that feature sounds to good to be true. (People sometimes make tiny changes to each post when they multipost, too, but at least it would get the great majority.)
As it happens, that exact feature is something that our software vendors hope to introduce on a future version of the program.
So maybe this problem will eventually go away.
hopehopehopehopehope
Gaudere said:
And that doesn’t even include the ones that I quietly clean up, without so much as a complaint…
The problem with CGI is that every call to a CGI program has to spawn a new process on the computer. This takes time. If the web site is on a single server, you can run out of resources pretty fast, in which case each CGI request will be queued, and this is probably what’s slowing the thing down.
If that’s the case, you can’t do anything in the CGI itself to speed it up, because the CGI hasn’t even loaded yet. All you can do is re-configure the machine to handle more processes (primarily by increasing RAM), or move to a multi-server configuration, which the software may not support.
Gaudere:
But if there isn’t a doublepost, you don’t know that the poster pushed “submit” twice, now do you? So of course the only cases of people pushing “submit” twice are people that have doubleposts. I’m pretty sure that I’ve had posts disappear more ofdten than I’ve doubleposted.
You could check for a certain percentage not quite 100%.
Hopefully that’s still so, but FWIW, it’s happened to me twice in the past few days. (It had never happened to me before, to teh best of my recollection.) The second time (on the MPSIMS “Satan’s Summer Shindig” thread), you can see a post where I wonder aloud whether to trust the CGI. (The post it referred to never appeared, so I wound up retyping it.)