Fastest LB, OneConnect and...
Hi,
I am a bit lost when it comes to terms used for Fastest LB description. Basically it described as based on outstanding L7 requests. But what exactly is that mean? If we talking about HTTP L7 request is equal to HTTP request? What in case of other L7 protocols like FTP or SMTP etc.?
The other are I am not sure about is how it relates to TCP connections (L4). As far as I understand when no OneConnection profile is used (at least for HTTP) LB decision is made once for each TCP connection. In case of HTTP/1.1 one TCP connection can contain many HTTP request (and replies) so how Fastest will handle such situation? It will increase outstanding counter only when first HTTP request is send over given TCP connection or it will be increasing counter for each HTTP request send over this TCP connection?
What about situation when OneConnect is used? According to docs in this case LB decision can be made for each HTTP request instead of each TCP connection. Will then Fastest count each request even if on the client side there is just one TCP connection transporting many HTTP requests?
Piotr