Queuing traffic in iRules - advisability!!

suspending commands like after and RESOLV::lookup are parked outside the event loop so they do not harm them flow while waiting for actions to occur. For non-suspending commands, like while and for, everything gets stacked behind that bus. A while loop that cuts through 200 counts, really no big deal. However, we've seen people (and by people, I mean me before I was edumacated on this!) suggest or implement for loops that bleed for seconds or longer, and at some point daemons get involved and bad things happen.

Colin wrote up connection state & suspension concepts a while back, hopefully this will help.