gusarov / river Goto Github PK

1. higher speed due to binary nature of HTTP/2
2. consistent server-pushed responses (in contrast to current implementation that breaks HTTP/1.1 spec)
3. multiple standardized identified streams in one connection

Implement Happy Eyeballs to fallback from IPv6 if it is not supported by the next party.
IETF promotes that IPv6 should be the preference when choosing among 2 addresses. But the next party (your ISP) might not support it. So:

1. on a IPv6 enabled machine you can receive AAAA dns entry for www.google.com but if you continue with IPv6 over SOCKS it might fail on a proxy server side if proxy's ISP is not supporting IPv6.
2. if you are connecting private machine it might have local IPv4 which is unreachable by proxy, while reachable by IPv6.
   To facilitate this, there should be Happy Eyeballs or similar implementation: Happy Eyeballs attempts to establish connection with both algorithms simultaneously. If IPv6 succeeded, it proceeds with IPv6 otherwise falls back to IPv4.

For the PROXY server in the middle this have one more option: proceed with Domain Name instead. This one also should be considered for better connectivity