@gargron @lain I suppose a keep-alive approach would work well too. I hadn't thought much about that. Maybe that is better.
The main upside of a websocket approach is cutting out some http headers in that case I guess then?
@cwebber @lain I’m going to wager that most gains are in the DNS/TLS handshake and not in headers. Mastodon’s delivery performance literally doubled when I added keep-alive multiplexing.
Gregory's Server
@cwebber @lain I’m going to wager that most gains are in the DNS/TLS handshake and not in headers. Mastodon’s delivery performance literally doubled when I added keep-alive multiplexing.