4 ms·
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_tr
by papaf 6y ago
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#Symmetric_NAT https://en.m.wikipedia.org/wiki/Network_address_translation#...
- rightbyte 6y agoI am not that much into mobile. Does TCP have the same difficulty?
- papaf 6y agoNo, as long as the connection is initiated by the mobile device, TCP is much easier.
- toast0 6y agoTCP, 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)