One extra benefit that I just thought of today (but haven't verified via traces yet) is that I believe OneConnect can help back end throughput as opposed to just helping with the setup/teardown overhead.
If your're doing lots of quickly-served, short connections, it's possible that they don't stick around long enough to get out of the slow-start phase of a connection. But if you've got a OneConnect socket that has been around for a while and moved a bunch of data, you'll be well past the slow-start phase and pushing data optimally across that socket.
Obviously HTTP 1.1 keep-alives should have the same effect...
--Matt
Cumulonimbus
