persist based on cookie with URI pools

Thanks for the reply. We avoided the cookie function to support folks who don't accept cookies, this is why you see the ";jsession" string in URI's.

 

 

We're only using seperate pools as a way to "count" the connections of .seam requests seperate from JPG/CSS/JS/etc files; we'd like the expensive requests more equally weighted. We're flexible on what technique to use for this, using two seperate pools with the same nodes just seemed to most obvious at the time.