image I posted an article yesterday about Disabling iRule Event Processing, and didn't really realize until after it was published how brill it was (JK ;^)

But seriously, it struck me after discussing it further with a co-worker that this solution has broader possibilities for other applications & protocols that may require selective iRule processing, specifically those for which we have protocol triggers and typically carry multiple requests per connection.  (The example used HTTP, and SIP springs immediately to mind.)  While you can use conditional statements to control iRule processing against any connection or request, disabling processing in specific events until it's needed again might be a good optimization to consider.