Session Persistent based on the HTTP Header

Really appreciate the quick response from Vernon and I am doing some research over that direction on the area of UIE (Universal Inspection Engine) in order to fit our project application requirements. As far as the details application requirements are concerned, we would like to take one step further as follows: The application server will in fact provide two pieces of information on the "HTTP Header", one of them is the "iSession" with a running session number for session persistent purpose. The other one is the "Priority Group Indicator" e.g. "iPGroup" which includes the Priority Group information One or Two (We are going to implementation two priority Groups" in our environment. Also, within a priority group, we will load balance the traffic according to a predefined Ratio for the pool members. The whole application logic would become : If the HTTP request contains the parameter "iSession" with the running unique session IDs, the LTM will route and persistent traffic to a particular node/pool member else If the HTTP request contains the parameter "iPGroup", the traffic will be forward to priority group define in the "iPGroup" value. Meanwhile, within the priority group the traffic will be load balanced to the group pool members according to a predefined ratio (e.g. 30 % / 70 %) for the two group members that belong to that group. end We would like to know if the UIE (Universal Inspection Engine) iRule <<********************>> when HTTP_REQUEST { if { [HTTP::header exists iSession] } { persist uie [HTTP::header iSession] } } <<*******************>> can combine with the logic of "Priority Group" as well as "Ratio" load balancing for the pool members and if so how can it be implemented. Your kind advice is much appreciated. Thanks & Regards Patrick