Hacker News Reader

Full thread

rightbyte

So much effort to do UDP over HTTP ...

No wonder they need 1000s of SWEs.

View on HN

So much effort to do UDP over HTTP

UDP on mobile networks is a royal pain because of symmetric NATs [1]

[1] https://en.m.wikipedia.org/wiki/Network_address_translation#...

I am not that much into mobile. Does TCP have the same difficulty?

No, as long as the connection is initiated by the mobile device, TCP is much easier.

TCP, especially on well known ports 80 and 443 is almost definitely going to work, if the network is going to allow any traffic. UDP might be blocked, and there's no well known ports more likely to work than others.

Other than that, NAT timeouts for UDP are probably a lot lower than TCP, so you likely need to ping more often to keep things active (but you should track this by network and adjust accordingly)

You saw their network reliability requirement right?

Ye, "Poor connection stability".

I don't see TCP/HTTP as a reliable protocol over unreliable networks. I mean they are sending hearbeats over HTTP. It is silly.

Reply on news.ycombinator.com