Hacker News Reader

Even with TLS 1.3 the fastest handshake for an initial connection is one round trip. That's around 250ms for someone connecting to a server in New York from Sydney Australia. Is there any other way to reduce this handshake time for visitors located geographically far from the server with end to end encryption?

View on HN

Under what circumstances would the initial connection need to be faster than 250ms for arbitrary HTTPS access? I can think of maybe it mattering to people that work with financial data, but outside of that I can't really see it mattering.

Loading a bunch of assets from different servers in a serial or semi-serial (e.g. 6 at a time) gets really impacted by that.

Loading bunch of assets from different servers to enter a site is a very bad idea.

Cross region load balance is probably only thing, although I understand you've asked for far distance.

Reply on news.ycombinator.com