Queuing traffic in iRules - advisability!!

Thanks Jason - that's an interesting suggestion and I'll look into it, but I just need clarification that even with 'after' now being a suspending command it's still not recommended running loops of 'after' statement?

Wouldn't the previous concerns from 2008 "iRule execution is single-threaded, so if you did somehow pause execution (like run a tight wait-loop as someone suggested), then you would be holding up all other packet processing. The multiple watchdogs on the LTM would notice this, and take appropriate action (restart tmm, or failover, or reboot, or some combination thereof)." be nullified now that 'after' is suspending?

I've done some medium-level testing where I've had 50+ queued connections all running the after loop and no watchdog processes kicked in, although perhaps I wasn't running enough traffic to trigger that behaviour.

Are there other concerns that I haven't taken into consideration?