enabling tcp multiplexing

There is no short answer in my opinion.

 

OneConnect will be the choice if you are dealing with http.

 

It will help you to multiplex requests on different incoming clientside connections onto a single serverside connection (aka connection pooling).

 

On the other hand it is also capable to demultiplex requests from a single clientside connection into multiple serverside connection (aka request switching).

 

As far as I understand, OneConnect is designed for to handle http only.

 

To multiplex / demultiplex other L5/L6 protocols on a tcp connection, some iRule logic will be required. Challenges are there especially with the handling of synchronous and asynchronous traffic and proper mapping of requests and responses.

 

I.e. with http it is expected to receive an answer before sending a new request through the same http keepalive connection.

 

With LDAP it may happen that a server is still busy with the previous query while the client is already sending the next one through the existing LDAP bind.

 

This means to me, that tcp multiplexing requieres to take care of the upper layer protocols. Otherwise there is a very good chance to break things ...