persist none for all pool connections when only one member is active (tcp only)

Thank you, Spark. The Election Hash irule is extremely useful in that it would only break persistence if the number of active members changed (eliminating overhead for session failover on the server in most cases). Also, it works when considering source IPs as well. My only question would now be, in what event would I place the logic? I completely agree that offloading SSL on the BIG-IP is useful and preffered. We typically do this in most cases. Unfortunately this isn't a typical application, and I've already lost this battle. As a result, I can't use the HTTP_REQUEST event. Should I use CLIENT_DATA (Is this too expensive)? CLIENT_ACCEPTED only triggers when the connection is first created, so it wouldn't allow me to rebalance existing connections. Any recommendations?