Sorry about the wrong attribute name -- you are correct (as stated on the wiki) that it is minHitTime.
FYI, I may not be entirely correct on the exact workings of CFThrottle. I read and interpreted the code instead of trying to devise some intricate test plan. If you want to see what's going on in the code too, it's in the: com.naryx.tagfusion.cfm.tag.ext.cfTHROTTLE class. I'm mentioning it here because it took me forever to figure out where the Java class was buried in the hierarchy. .pjf ziggy said the following on 11/12/2009 09:31 PM: > Good info, thanks! > > So, if I understand, I can set the minHitTime attribute to 0 and it > should ignore that line. I'll try it! > > By the way, you wrote both minHitTime and HitminTime (in the code). I > assume the former is right? > > > On Nov 13, 10:19 am, "Peter J. Farrell" <[email protected]> wrote: > >> I looked that the Java code and I think I see they this is occurring. >> There is an additional attribute for cfthrottle called "minHitTime" >> which defaults to 500 (ms). >> >> In cfthrottle is there is a shortcut in the condition aptly named quick >> throttled. It appears that if the lastHit occurs too soon you are quick >> throttled. >> > > > > --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
