Flood Control Message
Jul 2, 2001 | 9:34 am
#1
Original Poster
FlyerTalk Evangelist
Join Date: Mar 2000
Location: West Seattle, WA
Posts: 10,469
Flood Control Message
I received this message for the first time today.
You can only post 1 message a minute? This was weird b/c it was my first post of my session!?! Has this happened to anyone else?
You can only post 1 message a minute? This was weird b/c it was my first post of my session!?! Has this happened to anyone else?
Jul 2, 2001 | 10:06 pm
#5
Join Date: Nov 1999
Location: SFO
Programs: UA 1.050MM, PersonalCar 0.275MM
Posts: 1,720
That "feature" caught me the other day, when I posted two replies within 60 seconds. (Not just on two different threads; in two different forums, even! 
)
Although it got slightly in the way, it was no big deal to wait a few seconds, and it doesn't happen very often under legitimate, non-accidental usage patterns.
)Although it got slightly in the way, it was no big deal to wait a few seconds, and it doesn't happen very often under legitimate, non-accidental usage patterns.
Jul 7, 2001 | 1:31 pm
#8
Founder of FlyerTalk
Join Date: May 1998
Location: Colorado Springs, CO
Posts: 6,540
The Flood control is in place to catch duplicate posts when members accidentally hit the reply a few times in a row. No attempt to limit the number of posts by member. We choose 60 seconds as we thought it would allow the maxinum time for a server to react even under heavy stress.
Jul 10, 2001 | 6:11 am
#9
FlyerTalk Evangelist
Join Date: Sep 2000
Programs: DL PM, Marriott Gold, SPG Gold
Posts: 12,004
<font face="Verdana, Arial, Helvetica, sans-serif" size="2">Originally posted by Randy Petersen:
The Flood control is in place to catch duplicate posts when members accidentally hit the reply a few times in a row. No attempt to limit the number of posts by member. We choose 60 seconds as we thought it would allow the maxinum time for a server to react even under heavy stress.</font>
The Flood control is in place to catch duplicate posts when members accidentally hit the reply a few times in a row. No attempt to limit the number of posts by member. We choose 60 seconds as we thought it would allow the maxinum time for a server to react even under heavy stress.</font>
Jul 10, 2001 | 8:24 am
#10
A FlyerTalk Posting Legend
Join Date: May 1999
Posts: 46,817
Actually, I'd actually suggest going down to 30 secs! The reason I note this is that when things are really bad, (really, REALLY slow, and that is fortunately very rare), is when we appear to most need it, it but when it will not do the job very well since the lock up yields no feedback and one will very likely press return again - and again. We have seen this in the past when 5-10 posts were made over a 30 - 50 min period. So even 5-10 mins would presumably result in little additional gain - yet it will possibly help to discourage too much posting by any individual, in too short a time!
The real trick, IMHO, is simply to press the return key just once!
The reason I note this is that when things are really bad, (really, REALLY slow, and that is fortunately very rare), is when we appear to most need it, it but when it will not do the job very well since the lock up yields no feedback and one will very likely press return again - and again. We have seen this in the past when 5-10 posts were made over a 30 - 50 min period. So even 5-10 mins would presumably result in little additional gain - yet it will possibly help to discourage too much posting by any individual, in too short a time! The real trick, IMHO, is simply to press the return key just once!
