PERSIST at the pool level only

Yeah,

 

if not /streamer client A then pool A else pool B (then set a session cookie to route faster for subsiquent requests)

 

if /streamer and client A, then pool A2 + PERSIST else pool B2 + PERSIST

 

 

I'm shooting for 4 pools, A1/A2 and B1/B2...the 1's would be Observed method (best that I found for regular web requests) and the 2's would be least connections since all of the /streamer connections are long running and I just want to balance based on connection count and not performance like Observed offers.

 

 

make sense? sound like a clean solution?