PERSIST at the pool level only

I created an iRule for selecting the proper pool based on who's making the request, but now I have a question....we use a VIP for multiple products, each running in their own IIS app pool. One of them uses a long-running HTTP request for doing a publish/subscription type transaction where we push an update out the connection...which is using the PERSIST function to stay on a single server in the pool (the PERSIST iRule is watching for "/streamer" requests only).

 

 

How can I have both of these running at the same time?

 

 

What is the order of events with the PERSIST setting/profile and the rest of the iRules?