How to Limit concurrent sessions in a LTM using Irule

This is an older posting and perhaps setting connection limit was what was desired to keep the number of connections below 500 on each server. But from my understanding this doesn't keep more than 500 x number of pool members (if all set to 500 limit) from occurring. It is simply a way to load balance to maintain some limit. I have used this with priority pool members to keep connections on a set of higher priority servers until the overall limit is reached and then it spills over to a second priority set of servers. In both cases it won't keep more than 1000 connections (in this case) from occurring as it doesn't deny connection once a limit is set.

But if this question is to limit the number of application sessions (not connections), that cannot be accomplished, from what I understand, by setting a connection limit. An application session may connect and disconnect many times through the course of the application session. Denying that application session a connection due to a connection limit would interfere with an active user to server session. That can be done in an iRule.