4 ms·

Not if you send "noop" messages.

• dnautics 5y ago
  In my experience, sse times out way more than ws, even if you are always sending (I was streaming jpegs using sse).
  • bullen 5y ago
    I think it might be your ISP. For example one of my ISPs cut off my SSH connections no matter what I do. They simply dislike hanging SSH connections. It's just random that your ISP like WebSockets more than long HTTP responses, and it can change in a heartbeat and for most people it will be different. As I said before 99,6% successful networking is an unheard of number for real-time multiplayer games. I only care about that number, until you proove with hard stats and 350.000 real users from everywhere on the planet that WebSocket has 99,7% success rate, I'm not even going to flinch.
    • dnautics 5y ago
      It's not random. Having limited timeouts for http is policy set at often time several layers to prevent certain types of security regressions.
      • bullen 5y ago
        Ok, what security regressions?
        • dnautics 5y ago
          I am sure you can figure it out. I'm not bullshitting you.