How much more strain would a "compare post to previous by same user" add to the servers?
It's just not necessary to have the issue of double posts, since they are due to delay over the net and the user clicking twice or more on the Post button.
If it is too much, why not change the code to deactivate the Post button as soon as it have been clicked once?
The latter is less precise, a post could get lost, why I think a simple content comparison between last post and sent post would be the best solution.
It will in the end save DB space, energy, and ultimately some trees somewhere.
mike69spain: How much more strain would a "compare post to previous by same user" add to the servers?
It's just not necessary to have the issue of double posts, since they are due to delay over the net and the user clicking twice or more on the Post button.
If it is too much, why not change the code to deactivate the Post button as soon as it have been clicked once?
The latter is less precise, a post could get lost, why I think a simple content comparison between last post and sent post would be the best solution.
It will in the end save DB space, energy, and ultimately some trees somewhere.
Ok Mike....I think you have way to much time on your hands.....someone give that guy a spade.....
mike69spain: How much more strain would a "compare post to previous by same user" add to the servers?
It's just not necessary to have the issue of double posts, since they are due to delay over the net and the user clicking twice or more on the Post button.
If it is too much, why not change the code to deactivate the Post button as soon as it have been clicked once?
The latter is less precise, a post could get lost, why I think a simple content comparison between last post and sent post would be the best solution.
It will in the end save DB space, energy, and ultimately some trees somewhere.
Awesome suggestion, Mike. I find double threads and double or triple posts annoying, but I do understand that the people it happens to find it embarrassing, too. Having the post button deactivate as soon as it's hit once would be a brilliant way to stop this aggravation for us all.
druidess6308: Awesome suggestion, Mike. I find double threads and double or triple posts annoying, but I do understand that the people it happens to find it embarrassing, too. Having the post button deactivate as soon as it's hit once would be a brilliant way to stop this aggravation for us all.
It's usually not intentional. It doesn't really bother me, just a second chance to read the message
druidess6308: Awesome suggestion, Mike. I find double threads and double or triple posts annoying, but I do understand that the people it happens to find it embarrassing, too. Having the post button deactivate as soon as it's hit once would be a brilliant way to stop this aggravation for us all.
Just to clarify on double, triple or more posts....some computers when you hit the post reply click sometimes it clicks a number of times resulting in multiple posts.....no one means to do this it has happened to me on a coule of occasions I cant expalin why but it was never intentional and I imagine the same happens to others....
mike69spain: Sarcastic comments is not under proprietary laws, anyone can use them, me too.
As for the actual problem, it only occurs sometimes when the post function does not manage to "bounce back" to your browser in time, caused by lag of some kind.
I never tried to recreate it, but when on a very slow connection, I need to have two windows open, one where I check if the post went through, apart from the message window.
All in all, this post was not so much for the public as it was a suggestion to the CS programmers.
I was'nt being sarcastic......and I have posted much of what you said in my previous post....
stefonline: Just to clarify on double, triple or more posts....some computers when you hit the post reply click sometimes it clicks a number of times resulting in multiple posts.....no one means to do this it has happened to me on a coule of occasions I cant expalin why but it was never intentional and I imagine the same happens to others....
stefonline: Just to clarify on double, triple or more posts....some computers when you hit the post reply click sometimes it clicks a number of times resulting in multiple posts.....no one means to do this it has happened to me on a coule of occasions I cant expalin why but it was never intentional and I imagine the same happens to others....
I understand that it's never intentional, and why it happens is above my technical skill...but apparently Mike is tech-savvy enough to understand why and is offering a suggestion to the site programmers. I think it's a good one. He wasn't criticizing anyone here, nor was I.
And I wish I could skip over those multiple posts without reading them, but I'm such a fast reader that while I'm skipping them, I'm reading them. (Just a little side note about me, and one of my oddities.)
Report threads that break rules, are offensive, or contain fighting. Staff may not be aware of the forum abuse, and cannot do anything about it unless you tell us about it. click to report forum abuse »
If one of the comments is offensive, please report the comment instead (there is a link in each comment to report it).
It's just not necessary to have the issue of double posts, since they are due to delay over the net and the user clicking twice or more on the Post button.
If it is too much, why not change the code to deactivate the Post button as soon as it have been clicked once?
The latter is less precise, a post could get lost, why I think a simple content comparison between last post and sent post would be the best solution.
It will in the end save DB space, energy, and ultimately some trees somewhere.