iRules for TCP break up

You should probably not detach (issue the notify request) until after you have received the response from the server. Your rule currently issues the notify request at the beginning of the next request which potentially causes the detach before a response may have been received from the server. The only course I believe you have is to buffer or delay processing of the next request until you have received a response from the currently connected server. Though we have talked about designing a multiplexor where you could service multiple back-end connections at the same time (either repeating or load-balancing), this is not currently available. One-connect provides an already established connection to save the cost/time of establishing a new connection. It doesn't provide a means of concurrently sending data to multiple servers and then reaping the responses from all the servers it sent requests to. Sorry, but you'll have to stick with your first rule implementation.