iRule as stored function or similar

Actually, we've discussed this quite a bit in designing iRules.

 

 

The work-around is to use variables to pass arguments into an iRule and get returned results and then use priority assignment and multiple iRule combinations to chain the rule snippets together on various virtual servers. I've yet to encounter a situation where this doesn't provide the ability to write one rule that does common functionality and use it in various ways.

 

 

The decision to not have procedures was largely due to the impact on performance that making a procedure call has in Tcl.

 

This may someday be worked around...