dueling protocol profiles

Hello

We're trying to use an LTM to balance queries to a pool of Redis slave servers, and my dev's are having issues with the client library when it comes to connections being closed by the idle timeout on the LTM. The client is not reconnecting correctly.

So what I'm wondering is if its possible to use two different protocol profiles, one for the client with a very long idle timeout, then a normal 300 second timeout on the server profile. What I'm hoping this achieves is to allow clients to maintain their persistent connection to the LTM, then have the LTM open a new connection to whichever pool memeber is next to receive it based on the algorithm (e.g. least connections). This will then correctly balance traffic instead of maintaining a very long persistent connection between the client and the server, which breaks balancing.

From what I've read, there is in fact a separate connection from the client to LTM, and from LTM to server. But also it seems that the lowest idle timeout setting for any applied profile applies to the entire virtual server. So I'm a bit confused.