Site Issue - Resolved Flood Control
- Thread starter Evil Eye
- Start date
- Status
This is exactly what causes duplicate posts in some forums. 
Especially in forums where the server must contact another site for post information. The delay involved in doing that can result in accidental duplicate posts because the first one is not yet posted when the second one is started. Since contacting other sites can be a time consuming thing, it may or may not be possible to reduce the flood control time.
In the next few days, I will start slowly reducing the flood control time to see if we can reach a happy medium. But 1 to 2 seconds won't ever be a choice, I can guarantee that because it takes at least that long to establish a connection with another server.
Especially in forums where the server must contact another site for post information. The delay involved in doing that can result in accidental duplicate posts because the first one is not yet posted when the second one is started. Since contacting other sites can be a time consuming thing, it may or may not be possible to reduce the flood control time.
In the next few days, I will start slowly reducing the flood control time to see if we can reach a happy medium. But 1 to 2 seconds won't ever be a choice, I can guarantee that because it takes at least that long to establish a connection with another server.
Last edited:
To be perfectly honest with you, the only way I could duplicate what we were seeing with flood control disabled was by delaying connection to the other servers/sites and either refreshing or posting the same link multiple times. And that is the key, any delay in connecting to the external server/site could cause someone to believe there is a problem causing them to either repost, or hit refresh (and respond to a message something like 'The data must be resent').
I'll give a fairly basic explanation what happened when I simulated what was happening here...
1) I supplied a link or ID when creating a thread and click create thread
2) A program starts and checks if that ID was already posted
3) If it hasn't been posted, the program continues and connects to the other server
4) If the other server/site doesn't respond quick enough and I repost the same link, a second task starts at 1 and starts another thread being posted.
5) Both instances of the program continue to run and post the same information resulting in a duplicate thread.
This is exactly what we were seeing here. It is purely accidental and not something that could normally be done when flood control is enabled. The duplicate posts could not take place because it is prevented by flood control.
I'll give a fairly basic explanation what happened when I simulated what was happening here...
1) I supplied a link or ID when creating a thread and click create thread
2) A program starts and checks if that ID was already posted
3) If it hasn't been posted, the program continues and connects to the other server
4) If the other server/site doesn't respond quick enough and I repost the same link, a second task starts at 1 and starts another thread being posted.
5) Both instances of the program continue to run and post the same information resulting in a duplicate thread.
This is exactly what we were seeing here. It is purely accidental and not something that could normally be done when flood control is enabled. The duplicate posts could not take place because it is prevented by flood control.
- Status